Hey there 👋. Do you want to make a breakthrough? Do you want to be disruptive? Need to find a problem for your next hackathon? This is for you.
The Goal
In our everyday work, we are usually stuck iterating over previous solutions. As the machine rolls, it slows down with debt (technical, emotional, procedural), causing laziness and a lack of energy. This article is meant to help you create a new machine (whether that'd be a hackathon, new idea, new process, new spirit, new anything), one that disrupts the old way of doing things, making you and others around you more effective, happy, productive, inspired, etc. We can optimize this process by creating guideposts for strategy, unbounding the spirit, and explaining the theory behind it.
The Guideposts to Strategy​
By setting up guideposts to strategy, we can create an environment that harbors optimal design. The 3 guideposts to strategy are the diagnosis, guiding Insight, and action.
Diagnosis​
Every problem needs a proper doctor's diagnosis. To get a proper diagnosis, you need to clarify the target objective.

Creativity is a very messy process because there can be multiple target objectives (and even subtargets), all of which can be unclear. To clarify the target objective(s), take into account the social dynamics, technical implementation, and business values. For each part of the problem, you'll recognize that the bullseye becomes clearer when constraining yourself to limitations and by answering open questions / resolving ambiguity.
I have a very open ended example of "what should I do this weekend?". Observe how there are multiple target objectives.
Social Dynamics​
Everyone has to take into account social dynamics for their respective situation. However, what every social dynamic has in common is that they require cooperation. We can optimize it through optimizing knowledge transfer and visibility.
Knowledge transfer​
Problems can be complex and no on understands the problem as well as you do. It is crucial that you can get others to recognize the problem in order to get as much support from managers and onboarding by other engineers.
- Record your meetings. Take succint meeting notes from the meetings and derive Insight from the meeting notes.
- Standardize the way you get your point across. When writing a slack message, make sure the slack message is concise, does not have big words, and is properly sectioned.
- If you are hosting a meeting, make sure that the conversation stays on track.
- Create high level -> low level descriptions of the problem. This is important so that you can easily tell a manager the problem in a high level way. And when you need to talk to an engineer, you can explain the problem thoroughly to them.
Visibility​
Make all of your work public! Post your meetings to your message boards after they are done. Post your meeting notes and insight. Let everyone know what you are doing via your planning tool, like JIRA.
Memetics​
The most powerful thing that you can do to get others onboard to your initiative is through the concept of memetics. Memetics simply means having an idea spread like a virus. The best way to have an idea spread like a virus is to tell a story. Tell a story about you initiative. Make it dramatic. Put your passion into it.
Memetics is where the word 'meme' come from!
Technical Implementation​
Every problem that needs to be solved requires a technical implementation. It is important to be able to distill the problem in a high level way as well as low level.