Makestorming: 3 tips for a successful first “corporate hack”
Frenchweb publishes the good sheets of the new book by Marie-Noéline Viguié and Stéphanie Bacquere (“Makestorming: le guide du corporate hacking”, Diateino, 2016). This book offers a roadmap for hacking your own business and changing your relationship to work.
Read: Makestorming for collaborative work
After a little theory, it’s time to take action! We recommend that you deploy makestorming in three stages: succeed in your first hack by relying on a project, change your daily attitude to establish new working relationships and finally play the network effect to take to another scale and transform corporate culture.
Before getting your hands dirty, here’s a quick update. Or a reminder. You remember ? When we defined makestorming, we talked about an approach. The term is not innocent. We could have defined makestorming as a method. In this case, this book would have had a title catchy of the kind : “Hack your business in 5 steps”, For example, as if the same method could be applied to all companies without looking at their context. And behind, we would sell standardized missions, taking refuge, in case of failure, behind the favorite excuse of old-fashioned consultants: “Ah yes, but it’s because you haven’t applied the whole method!”
In short ! If we have defined makestorming as an approach, it is because it is a new way of approaching things. It is not a miracle recipe, because miracle recipes do not exist. Nor is it a uniform method, which would be imposed on everyone in the same way by cascading down from the management floors. Because a ready-made method does not teach you to think, it does not empower. On the contrary. However, this is what we are defending: individuals who think and create instead of just functioning, an understanding of situations to be found, an autonomy to be conquered, a work culture that spreads in bottom-up mode when leaving of concrete projects, and which goes viral thanks to its successes. In short: makestorming is based on principles, tools, techniques. It is mainly based on attitudes. It is up to everyone to seize it, or to be inspired by it!
Succeeding a first hack on a project, adopting the attitude of the corporate hacker, building a community to viralize the hack: the following pages are filled with advice and practical exercises to move more quickly from idea to action. Everyone is free to take them in order, or to draw from them according to their needs at the time; Everyone is free to do the exercises or not: we are not here to check knowledge, we are here to give you an impetus, and to mark out a path that you will build yourselves.
Oh, and one last thing: after a hundred pages spent together, now that you are ready to wet your shirt and hack the company’s operating system … We could perhaps be on familiar terms, right? Hang on, we’re going!
Hack your projects
“The action precedes the action plan …” Yes, but that does not prevent you from asking yourself a few questions before launching the project which will dedicate your first hack. Here are some answers to the ten questions we are asked most often. You will find some basic rules, practical additions to the principles of makestorming, illustrations that can give you ideas… And above all tools: practical exercises to take action.
Which project to choose for a first hack?
From the internal micro-project to the strategic plan of the company: we can train on any type of project! But you might as well start with a simple project, and increase the difficulty as you go.
Starts with a short project … or a piece of an ongoing project
For a first hack, don’t drown yourself in a big project. Preferably choose a project (or part of a project) over which you have control, and which does not involve the whole company: let’s avoid gas factories! Also preferably choose a short project – say, a few months … or less. If it is a medium-term project, start by breaking it down into mini-projects, with a first concrete and tangible objective. Also note that you don’t have to start from scratch. You can just as easily hack a current project, offering to work differently.
Find a project you like and believe in
What does “believe in” mean? It is having confidence in the success of the project, and in the fact that it can actually be implemented by the company. “Believing in it” is also putting self into your projects: not listening to your ego (there are only too many of them in companies, and they rarely advance the schmilblick), but your desire.
Makestorming: the guide to corporate hacking
Marie-Noéline Viguié and Stéphanie Bacquere
Marie-Noéline Viguié and Stephanie Bacquere met 10 years ago in the first 2.0 ecosystems. Relying on the strength of the working methods of digital communities, they have launched the challenge of transmitting them to large organizations by founding nod-A in 2009.
Both digital experts, driven by the culture of “hacking”, they combine their skills in design, entrepreneurship, engineering and collaborative work to draw the imagination of the work of this new century: a work where autonomy, meaning and collective responsibility are the key words.
They fight to awaken individuals to a different way of being at work. They encourage them to do more than talk, to play the collective more than just individual recognition and to hack the company to wake it up.
It is with nod-A that they show that it is possible. Companies, such as BNP Paribas, SNCF, Systra, or L’Oréal, have adopted their concrete and disruptive approach.