Start all of the pieces of work a little bit earlier. The key to starting work early is not succumbing to the pressure of having to finish the work. Don’t worry about finishing. If you’re a developer, you can start doing things while your design or information architect are working because a lot of your work actually isn’t dependent on their work. Some of it is, so you probably won’t be able to finish, but that shouldn’t stop you from starting.
Share Work-in-Progress Early and Often
When you share work-in-progress, share it with the caveat that no feedback is needed at this point. You’re simply sharing it to let people know where you are. For example, if you have to make 12 wireframes, share it when you finish 2 or 3. Rather than spending a whole week to drop 12 wireframes, share 2 – 3 wireframes every 2 days. The more often you do this, you start to build rhythm, and rhythm builds momentum.
We know strategy is an unfolding network of associations:
The evidence from the case suggests that the concept of strategy can be reappraised. From strategy as a static set of choices made at a specific point in time to strategy as an unfolding network of people, shared experiences and artifacts that is constantly being remade.
And we know that only 30% of employees can articulate a company’s strategy.
And I believe in the hyper-connected age we live in both of these things are becoming more true - that strategy is increasingly “in motion” and that most organizations are realizing their OODA loops are too slow for the modern world.
This causes the articulation of strategy to stall and get left behind - how do you articulate something in motion? It’s easier to write strategy down when it doesn’t change right?
As a result - there’s a widening gap between the perspective on strategy that the executive team has and the received ideas of the company’s direction that teams and employees have.