Selon un sondage récent de l’Ifop, 91 % des jeunes cadres français pensent que leur entreprise est en train ou va se transformer. Mais pour 47 % des entreprises, la transformation reste aujourd’hui synonyme de « digitalisation ». Elle ne concerne l’évolution du style de management que dans 21 % d’entre elles et la relation client dans seulement 20 %. Pourtant, ces cadres pensent que la priorité devrait être mise sur l’évolution des modes de rémunération des salariés (37 %), l’évolution des styles de management (33 %) et la formation et le développement de compétences (33 %).

Les jeunes cadres français ont bien compris que loin de se cantonner à la digitalisation des processus, la transformation concerne de nombreux aspects de la vie de l’entreprise, et surtout sa culture et son organisation. « Une entreprise ne peut réussir sa transformation digitale si elle n’a initié une profonde transformation en interne » explique Jean-Christophe Conticello, fondateur et CEO de Wemanity.

« L’apparition d’Internet et des technologies associées a bouleversé en profondeur le monde de l’entreprise. Les modes de consommation ont évolué, le temps s’est accéléré, ce qui a entrainé également une profonde évolution des modes de travail. La nécessité de changer est devenue vitale : on ne compte plus les entreprises qui, en hésitant à changer de recette, n’ont pas réussi à se renouveler et ont disparu : Kodak, Virgin Megastore, Nokia, BlackBerry, Yahoo!, etc. Non seulement, la nouvelle génération a compris cette nécessité de changement, mais elle le suscite avec les nouveaux modes de travail qu’elle privilégie. »

« Spark the Change » : décrypter et inspirer les bonnes pratiques  

Pour illustrer et expliquer cette évolution, l’événement « Spark the Change » a été créé à Londres en 2014 par Helen Walton et ses associés de Gamevy, avec le soutien de Wemanity, puis décliné en Australie, aux Pays-Bas, en Inde et au Canada. La première édition française sera organisée à Paris, le 26 juin prochain au Théâtre de la Madeleine.

Centré sur le futur du travail et les moyens de repenser l’entreprise de demain, « Spark the Change » propose aux entreprises françaises un programme de conférences de qualité, basé sur des retours d’expérience.

18 experts se succèderont sur scène pour décrypter les tenants et aboutissants de la transformation des entreprises. Parmi eux : Ludovic Huraux, CEO et fondateur de Shapr ; Dirk Ahlborn, CEO Hyperloop Technology ; Anthony Gooch Galvez, Directeur de la communication et des Affaires publiques à l’OCDE ; Anamita Guha, Product Manager, IBM Watson ; Marianne Syed, Executive Director chez Positive Planet UK. Et bien sûr, Arie Van Bennekum, seul rédacteur européen du Manifeste Agile, aujourd’hui Agile Thought Leader chez Wemanity et Jurgen Appelo, CEO et fondateur d’Agility Scales et expert du management 3.0.

3 thèmes principaux

Animées par des professionnels de toutes nationalités qui souhaitent faire évoluer le monde du travail, les conférences « Spark the Change » sont réparties dans trois sessions principales :

  1. Créer l’entreprise de demain : les différentes étapes pour insuffler un véritable changement dans l’entreprise, sur la base d’un apprentissage continuel, d’une maîtrise totale des technologies et d’une organisation plus agile et réactive.
    Jurgen Appelo, CEO et fondateur d’Agility Scales, expliquera notamment dans quelle mesure il est essentiel pour une entreprise d’aider ses collaborateurs à maîtriser continuellement le changement, par exemple via la ludification et d’autres nouvelles pratiques.
  2. Libérer les talents : développer le potentiel de chaque collaborateur, instaurer le bien-être au travail, booster la collaboration et créer un environnement de travail basé sur la confiance.
    Anthony Gooch Galvez, Directeur de la communication et des Affaires publiques à l’OCDE, détaillera ainsi « l’Indicateur du vivre mieux » de l’OCDE qui permet de comprendre ce qui contribue au bien-être des individus et des pays, et d’identifier comment susciter plus de progrès pour tous.
  3. « Sparking disruption » : privilégier l’innovation, voire la disruption ; remettre en cause le statu quo ; et valoriser le progrès social, technologique et culturel.

Dans cette session, Dirk Ahlborn, CEO Hyperloop Technology, dévoilera la genèse de la création d’Hyperloop qui, au-delà des records de vitesse et des nombreuses innovations qui le caractérisent, propose surtout de révolutionner l’expérience des usagers du train.

« Spark the Change a été créé pour inspirer les entreprises, à l’heure où elles sont confrontées à plusieurs évolutions stratégiques : la transformation numérique, l’évolution démographique, la co-innovation voire la “coopétition” sur des marchés mondialisés » explique Sabri Ben Radhia, Responsable de l’événement chez Wemanity. « Si Wemanity était présent lors des premières éditions internationales de Spark the Change en tant que sponsor, nous avons repris la marque et sommes devenus son organisateur principal. Réservé à la fois aux entreprises et aux institutions publiques, l’événement a pour objectif de couvrir l’ensemble des aspects relatifs à la transformation des entreprises, sur la base de très nombreux retours d’expérience. Il vise également à aider les entreprises à développer les compétences nécessaires pour mener à bien leur transformation ».

Le programme de la journée a été construit pour privilégier l’échange d’expériences et le networking. 750 personnes issues de l’ensemble de l’écosystème de l’innovation européen sont attendues le 26 juin prochain au Théâtre de la Madeleine.
Aurons-nous le plaisir de vous compter parmi eux ?

 

Plus d’information sur l’événement : http://sparkthechange.fr/about-us/

Les experts qui interviendront dans les conférences : http://sparkthechange.fr/speakers/

Inscription : http://sparkthechange.fr/tickets/


Also published on Medium.

Nine things I didn’t know nine years ago

May 19, 2016

 

Image from page 400 of “The Palm of Alpha Tau Omega” (1880)

It’s coming up on nine years since I first started slinging code in a professional setting. Professional here meaning with a salary, in an office, with other engineers, decent coffee and unreasonable deadlines.

Back then I was barely newly minted from school, and what I lacked in understanding I certainly carried in hubris. I remember being vaguely offended not to be on the list of Sweden’s top coders that year. No idea how they would’ve found me, but I still remember being annoyed by it.

What I’ve lost in hubris in the last nine years, I’ve gained in experience. I thought it’d be useful to punch down a few things that it would have been nice to know nine years ago — maybe it can help you, if you’re just about to take your first steps out of school.

In no particular order, here are nine things I wish I’d known when I started out:

  1. Experience counts for something. This is obvious, and maybe a bit condescending. But I remember the first time I saw a colleague in a live, heated situation pull up YourKit and hone in on the fact that we’d have two ServerInstanceFactories, not one, and that caused the entire app to go belly up. Or when I got literally smacked on the fingers for not using two-phased locking correctly. And a thousand other things. My first two years of working, what I mainly learned was that I basically didn’t know shit.
  2. People are messy. I’d love to know how many hours humanity as a total spends every day mediating between two or more angry 40-year old men. Most of the time, you’ll find reasonable people that don’t share your point of view on things, and you are not obviously right. There are tradeoffs. And sometimes people hold on to stupid ideas longer than they should, simply because they’re people. It’s a great irony that software development demands literal, logical, unambiguous reasoning while being complicated enough that you need to collaborate with ornate, arbitrary, ambiguous humans.
  3. You’re not logical, you’re biased. If there was one thing I was certain of was that I reasoned with logic and soundness and that I thought things because they were true. Things such as — we hire people only because of merit. Obviously. What I’ve learned is that any point can be argued from many angles, and who I am, where I was raised, what I studied and who my friends are all influence what I think is obviously true. I’ve also learned that I’ll likely never be Spock, and that the only reasonable defense is to invite different points of view, and accept that reasoning from different premises can lead to different conclusions, and still be logical and sound.
  4. You can use engineering for other stuff. As a flipside to above, I’ve also learned that the method of engineering that you learn in school and hone over the years is useful for a ton of other stuff than just programming. What engineering is to me is a way to define, decompose and reduce a problem space, and from that reason a solution under balanced constraints. Really, figuring out what you’re asking, and then answering that. And turns out that anything from sales, marketing, finance, design to analytics are super-susceptible to this. Don’t be afraid to dive in. It’s usually pretty simple to get stuck in.
  5. Users are not stupid. This one is a big one. When users complain about your product, it’s usually not because they’re stupid. Your dad, uncle or whatever that don’t really understand Facebook are not stupid. They just know other shit, and they haven’t learned this stuff yet. And that’s Facebook. They have literally hundreds of user researchers making Facebook simple. When your uncle doesn’t understand your app, it’s probably because it’s pretty unusable. Don’t blame users for that.
  6. Engineers have professional responsibilities. If you work with software in a company that makes money, chances are you have users. Even if you’re building Spotify, not a pacemaker, you still have a responsibility to your users. They’ve chosen your product, and if it sucks, they’re suffering and it’s your fault. This means that if you’re out chugging beer, the systems you maintain go down, and no one else can pick them up, you get a cab home and fix it. Obviously, don’t let a company take advantage of this responsibility. You should get reasonably compensated. But it’s still a responsibility. You can’t laugh off service disruption.
  7. Inverting a tree is useful, but not in the way you think it is. I’ve always been a strong believer in academic knowledge, and I loved taking the hardest courses. Particle filtering, non-linear signal processing, abstract algebra, advanced algorithms, etc. If it looked hard I wanted to know it. However, the point of Red-Black trees is not Red-Black trees. The point of graph traversal is not graph traversal. The point is, the tools you have shape how you solve problems. And the deeper the understanding of graphs you have, the easier it will be for you to see that a problem is a graph problem. Just like if you know enough economics, you can see business problems as market problems. And so on.
  8. Integrating early is always better. This is really mundane compared to all the other grand advice, but if you’re a bunch of people working on a piece of code, avoid branches and avoid submodules as much as possible. It’s really not better to work on your own branch until all is nice and then merge back. Merge early. Merge often. Otherwise you’ll spend a month merging. I promise. Like, I really, really promise … and actually, I guess there is grand life advice here as well. If you and someone you depend on disagree on something fundamental, don’t hold a grudge. Hash it out, as early as possible. Make sure you see eye to eye. The process and the product will be all the better for it.
  9. Simpler is literally always better. I saw someone write something like “Software engineers spend their first two years building complexity, and the rest of their careers managing it”. This is true. Really true. If you can avoid it, never write a dispatcher. Never write an orchestration framework. Don’t use Java if a bash script will do. Solve the problem you have now, not the problem you might have later. Nothing makes you feel as smart as a well architected, abstract framework for solving really complicated, general problems. Nothing makes you feel as stupid as not understanding how to debug it.

Anyway. This is my list. The nine things I wish I knew nine years ago. It strikes me now that current me would love to see the list Nine Things I Wish I’ll Remember In Nine Years. What stuff have I forgotten that would warp my perspective? I’d love to hear your take on either this, or what I missed on this list.

By: Marcus Frödin from Spotify

https://medium.com/@marcusf/nine-things-i-didn-t-know-nine-years-ago-fcbc757b268b#.9xksp8f8t

Scrum Gathering Orlando Through The Eyes Of A Live Illustrator

May 17, 2016

Equipped with my graphic board, pens, sunglasses and shorts I set sail for the Scrum Gathering in Orlando. Having attended two awesome gatherings in the past, the bar was set high – however, I was far from disappointed.

From the offset, co-chairs Anu Smalley and Kate Megaw knocked it out of the park by entering the stage to the sound of ‘Starman’ by David Bowie, whilst wearing convincing spacesuits complete with helmets. This was their genius way of setting the Gathering’s theme ‘Infinity and Beyond: Transforming the World of Work’. With three tracks on offer, ranging from beginner (‘Mission Control’), intermediate (‘Orbiting the Earth’), to advanced levels (‘Agile Galaxy’), there were more than enough sessions to choose from for all 1100 attendees. Let’s not forget that this was the largest Scrum Gathering so far.

Although each session had a unique offering, there was an obvious key topic that resonated from all talks. During the CST/CEC retreat ‘Agile Leadership’ was introduced as a pressing subject, with one attendee keen to highlight the distinction between ‘Leaders’ and ‘Managers’. Brian Rabon reminded everyone that ‘Agile starts with Leadership’ during his opening keynote. A panellist on the PWC keynote pinpointed that any organisation would struggle without ‘Agile Leadership’, and Steve Denning went on to inform the audience during his ‘Agile Leadership’ talk that the key driver for ‘Agile Leadership’ is having a different mindset.

Leon Sabarsky identified during his ‘Extreme Scrum Hiring’ talk that an obvious flaw when interviewing individuals for team roles is to interview them on their own. His key takeaway was to move away from ‘One-on-One’ interviews by considering ‘Scrum Team group interviews’. This approach enables individuals to be assessed based on their engagement within the group, and demonstrate the qualities required for being an effective team player. It all comes down to good collaboration and communication, folks.

Leon noted that:

“the number one criterion that Scrum team members ought to be measured against is their Collaboration skill. It’s relatively easy to teach people a domain area, Agile methods and a specific technology. However, I can’t teach someone to collaborate well. They either have it or they don’t. If they don’t, they will reduce team effectiveness and cohesion over time.”

Another talk with an interesting twist was ‘Scrum Team CRM: Aviation Crew Resource Management Techniques for Scrum Teams’ by Thomas Friend. Using the narrative of flying aircraft, Thomas made strong comparisons between ‘Aviation’ and ‘Scrum’. Once again, the underlying message here was good communication.

During the Gathering another inspiring movement was unfolding. A group of passionate Agile Educators met face-to-face to carve out a manifesto for Agile that is authentic to Education. With a variety of case studies demonstrating how Agile values and principles have been adopted within an educational setting showing proven success, this group of innovative leaders were making a difference. They set out to define a vision and values for what resulted in the ‘Agile in Education Compass’, an inspiring model for how education can respond to the modern world with agility.

Once again, I had the opportunity to take to the pen and draw key insights from beginning to end. The canvasses enticed the crowds, and people soon took to Twitter to share the learning and store the visuals as a reminder of the Gathering.

Alongside this, on the final day, I couldn’t resist suggesting an Open Space topic around the use of ‘Graphic Templates’ which can assist coaches and facilitators in communicating with pictures. The session was a great success and those that attended were satisfied with their newly gained visual skills.

“Visuals speak volumes, this workshop encouraged me to draw and take these skills back to my team.” – Lynda Menge (workshop attendee)

Whether you wish to enhance your facilitation skills, make collaborative design thinking a key enabler within your team, or simply gain the confidence you need to draw live in front of an audience, join me for a one-day ‘Innovation through Visualisation’ workshop in London on the 1st of June or Atlanta on the 24th of July.

My final point on what drives so many people to attend the gatherings: passion and the desire to collaborate and share ideas. People attend these fantastic events for the discussions and seeds of information that are shared over breakfast, and last well into the evening over a cold beer, the networks that grow, and the desire to continue to collaborate way beyond the event.

I look forward to sharing some ideas with you at the next Scrum Gathering.

By: Stuart Young from Radtac

http://www2.radtac.co.uk/blog/scrum-gathering-orlando-through-the-eyes-of-a-live-illustrator/

 

How the Future of Tech Impacts Work Habits

Apr 29, 2016

During the DevExperience conference on the 25th of March, we sat down with one of the key speakers, Lisette Sutherland, to discuss the ways in which technology advancements, and VR in particular, will impact people’s lives and working habits.

Beaglecat: Could you please tell us something about yourself and the company you run?

Lisette Sutherland: I am the director of my own company, Collaboration Superpowers. Myself and other licensed Facilitators give online and in-person workshops to help companies work better together remotely. I am also the remote team manager at a company called Happy Melly – a global network of businesses that are focused on making people happier at work (included are Management 3.0, my company, LeanChange.org, Improv Agility, and others).

BC: Do you think in 5-10 years we will have offices like we have today or do you think everyone will work remotely?

L.S.: Technology is making the traditional ”9 to 5” schedule unnecessary and less attractive for more and more people, especially the younger generation. The most important thing is working from where you are the most productive. Some people work better on the road, some at the beach, some from the office, some from the comfort of their own home – everyone should choose what works best for them.

BC: Do you think that we will be able to work using Virtual Reality in the near future?

L.S.: They’re already doing it. Virtual worlds have existed for more than 20 years now. People are going to school and earning degrees in VR. People are going to conferences in VR. The military uses VR for simulations.

The only issue is that navigating in VR is very difficult, it’s like learning to play the piano. That’s why it’s not so popular. It’s worth trying it out to see what it’s like to be in a virtual world. For example, you can create an account in SecondLife. When you log in, you are placed on a “newbie beach”, literally a beach for new people. Then you have to learn how to move your character and interact with the world and find your way to the place you want to go (like a conference).

BC: I am guessing that 10 years from now this is going to grow. How do you think this is going to impact us?

L.S.: One thing to be careful of is getting enough real life social activity. Technology has an addictive, unhealthy side to it. Each person needs to create healthy boundaries for themselves. The exciting thing is that with technology people can get together from anywhere in the world and solve interesting and challenging problems. I used to work for a company that was developing an online project management tool. The CEO was building it because he wanted to solve the problem of aging. He was frustrated that longevity scientists all over the world couldn’t properly collaborate together and easily share data. So he set out to build a tool they could use to collaborate at a distance. For me it was an ‘aha’ moment. I realized that if we could get the right people together, we could do great things like curing cancer or stopping global warming, or aging.

BC: What do you think the world will look like in 20 years?

L.S.: It is hard to say because if you asked someone 20 years ago what the future would look like today, they would have probably envisioned it completely different.

I recently held a workshop in Lebanon from the Netherlands using a robot – so I beamed into Lebanon, talked to the people as if I were there in the room. Drivable robots are also available now. For example, my friend from Canada beamed into one of these robots in Las Vegas, I beamed into another one from the Netherlands, and we both attended a conference as if we were in Las Vegas together. We visited booths, saw a presentation, had tea together, all from the comfort of our own living rooms. If you had told me I’d be doing that 20 years ago, I wouldn’t have believed you.

When borders dissolve, the possibilities really start to open up. For example, someone in Romania can work with a team in San Francisco, or a team in Vietnam. Sometimes you need that one guy or girl with that unique skill that nobody has – and what if that girl is not from the city you are working in?

There are also many people in the past that have been limited by location. For example, military spouses, disabled people or retired people. Military spouses have a hard time finding stable work because they are constantly moving. And there are many people who have retired, but still want to practice their craft or continue working somewhere. Because of remote technologies, there’s a whole new pool of people to choose from for the work that needs to get done.

BC: So do you think that in the future robots will do everything?

L.S.: I think robots should do the boring work and humans should do the interesting work. And maybe in the future not everybody will have to work full time, and maybe that’s ok. Do we have to work 40 hours a week? Why? That was a random number set by Henry Ford. Maybe we could work 20 hours a week and the rest of the time we could travel, or work on our hobbies, or spend time with our family, or just do whatever we want.

BC: What do you think is the influence of technology on productivity?

L.S.: Recently, I see a lot of companies struggling to go from being time-oriented to results-oriented. When we can work from anywhere, the focus is more on what you get done, not how long it takes you to do it. Spending the whole day at the office only means that you spent the whole day in the office, not that you were productive.

Summing up, the good thing about technology is that it dissolves borders but it requires a new way of working. What it means to be “present” at work is changing, and it’s opening a lot of new opportunities. A lot has happened in the last five years. I encourage people to explore some of the new tools and think about how they can use it in their own lives. My Work Together Anywhere Workshop is a great place to start.

Lisette Sutherland is Director atCollaborationSuperpowers.com, a company that helps teams work together from anywhere. She is also the remote team manager for the all-remote freelance team at Happy Melly.

Leave a Comment

Your email address will not be published. Required fields are marked *

Comment *