Turning vision into action is where most founders and tech leaders get stuck: too many ideas, too much incoming work, and not enough time to finish what matters. This guide brings together the four methods I use with clients, from shaping a raw idea into something testable to protecting the hours you need to execute.
If you have an entrepreneurial mind, ideas arrive all the time. Some are wild, some are practical, and some keep you awake at night until you write them down. At the same time the work keeps arriving: tasks, meetings, messages and decisions that all seem urgent. The result is a long list of good intentions and a calendar that leaves no room for any of them.
I have lived this as a founder, from the early months at the fintech company I co-founded to running operations at a spacetech startup, and I now help founders and technical leaders work through it as a coach. Over the years four methods have made the biggest difference:
- Turn an idea into something you can act on.
- Decide what has to change, and in what order.
- Separate what is urgent from what is important.
- Protect the time to execute.
1. Turn an idea into something you can act on
Every idea starts as a feeling: a picture, a sound, an “aha” moment. On its own it is not something anyone can act on. The work is converting it, step by step, from abstract to concrete. This is the flow I use for anything interesting that comes to mind:
- Capture the vision. Write it down as soon as it arrives, even if it is only a sentence. Unwritten ideas tend to disappear back into the abyss they came from.
- Get everything onto paper. Write down every related thought, memory and feeling. If you think in structures or relationships, draw them as diagrams. It will be messy, and that is fine.
- If you are stuck, change the medium. Explain it out loud, sketch it, or describe it as a story. A different form often unlocks what writing alone cannot.
- Pull out actionable points. Rewrite the draft as bullet points or user stories: who needs what, and why. Some detail gets lost here, and that is the point.
- Group them into an MVP. Pick the few points that are easiest to build and still show the idea clearly. The goal is something usable that creates a little value.
- Get feedback early. Put the MVP in front of clients or users before it feels finished.
Each step converts the idea from one form to a more concrete one, and each conversion loses some signal. These habits make the conversions more accurate:
- Have more customer discovery conversations. Nothing sharpens an idea faster than hearing how real people describe the problem.
- Step away. A walk or a workout lets your subconscious sort out inconsistencies.
- Combine the idea with something from your previous work, or imagine its exact opposite to see it more clearly.
- When you have nothing to write, write anyway until your mind offers a path forward.
Spend the least effort possible at each step so you get to the next version faster. When you catch yourself thinking “a few more days and it will be perfect”, stop and ask for feedback. Your intuition is useful, but it is also biased, and the longer you polish alone the more attached you become to one outcome.
2. Decide what has to change: a five-question framework
Some decisions are easy because you already know your answer. Others involve the future or a big change, and those are the ones that stall. For them I use five questions, in order:
- Where are we now? The current state of the project, the role or the resources.
- Where are we going? The future state: the vision, the target role, the ideal outcome.
- What will close the gap? The activities, experiments and experiences that move you from one state to the other.
- What does that require? Money, time, agreement from others, changes to the team or the calendar.
- What comes first? How these activities fit with everything you already have on your plate.
An example: a promotion conversation
A team member asks their manager for a promotion. These conversations happen all the time and are rarely easy.
- Now: Start from the person’s original job description, then talk about what they actually do day to day. Agreeing on this list puts you both on the same page.
- Going: Write down everything they want: more responsibility, a new title, more pay, flexible hours. Do not judge it yet. Then apply the real constraints, such as the next role’s definition, budget and timing, and agree on something plausible.
- Close the gap: Training, taking on one responsibility from the future role, or simply sitting in on meetings they were not part of before. This builds skills and lets you both test whether the new role fits.
- Requires: Adjusted expectations from colleagues, a changed team structure, time on the calendar. Framing these as temporary gives you both a way back if it does not fit.
- First: Decide which one or two activities start this month.
The same five questions work for a product roadmap, a reorganization or your own development. The last one is the hardest. People are good at dreaming and bad at prioritizing, because it means saying no to good things. It is also the step that turns a plan into a first move.
3. Separate what is urgent from what is important
In the first months of a company, new work keeps arriving before the old work is even started. Evenings and weekends do not close the gap, and every unkept promise feels like a risk to your reputation. Here is the approach I use when the workload is bigger than the hours.
Accept that you are in survival mode
An early-stage company is not a regular job. The goal is to reach product-market fit before the time or the money runs out, and that gives you permission to drop old habits and solve problems in new ways. Think racecar, not sedan: every part of your day is tuned for one goal.
Know your bandwidth
Learn how much you can really do in five minutes, an hour or a day. The better you estimate, the earlier you can see which tasks will not fit. Rest is part of the budget, not a luxury: building a company is a marathon, and skipping recovery works against survival.
Work with the waves
Work arrives in waves of chaos and calm. Use the calm stretches to prepare for the next wave: finish backburner projects, fix the work you are least proud of, and arrange your calendar for focus, for example with a meetings-only day and a meetings-free day.
Ask for help and delegate
You can ask almost anyone for help: friends, former colleagues, advisors. Keep each request precise, with a clear outcome, so people know when they are done. Thank them personally. Over time you will see which kinds of work need which kinds of people, and that becomes your delegation guide.
Let “good enough” be good enough
This is the hardest one for perfectionists. There is not enough time to perfect everything, so some work will ship with gaps and some will be dropped. Ask what the minimum is that still gives the customer value, and how much imperfection your early users will accept. Usually it is more than you think.
Set the criteria
Finally, decide explicitly which work keeps the company alive and which can wait. In survival mode, the work that brings in customers, cash and learning comes first. Improvements that make the ship run more smoothly matter, but not if the ship is sinking.
| Type of work | In survival mode |
|---|---|
| Keeps customers, cash or learning flowing | Do it now, yourself if you must |
| Needed soon, but others can do it | Delegate with a clear outcome |
| Makes things better, not possible | Schedule for the next calm stretch |
| Nice to have | Say no, for now |
4. Protect the time to execute
Treat your workload like a stream of random inputs that needs a processor. Sorting work by size makes it much easier to handle.
Size the work
- Quick tasks (under 30 minutes). If it takes less than a minute, do it now. Otherwise keep a running list and clear it in one batch at the start or end of the day.
- Medium tasks (2 to 3 hours). Block calendar time for each one, so other people cannot take it. Seeing them on the calendar also makes it easier to spot what you can delegate.
- Long projects (5 hours or more). Write a rough plan, scope and timeline, even if you are working alone. Then split the work into time chunks rather than project chunks: time chunks have a clear start and end. Put the hardest chunks at the time of day you think best, and keep them close together, because staying in the same context multiplies progress.
- Meetings. Keep them short, invite fewer people, and group them next to each other so they do not break up your deep-work blocks.
Tame interruptions
- In person. Being available is not the same as being interruptible. Ask your team to message you or book time, and agree on availability with your manager. Book meetings with yourself for deep work.
- Email. Almost nothing needs an instant reply. Turn off notifications and check at set times, for example on the hour or between meetings.
- Chat. Replying within a couple of hours is fine. Keep notifications only for the channels that truly need them. If something is urgent, people will call.
- Phone. Use Do Not Disturb with a short list of people who can always get through.
- Tools. Broken software and flaky internet are hidden productivity killers. Keep your tools simple, know who to call when they break, and have a backup connection.
Putting it together each week
- Capture new ideas as they come, and move one of them a step closer to an MVP.
- For any big decision, write down the five questions and answer them.
- Review your list against survival criteria: do, delegate, schedule or drop.
- Block your deep-work time and your batches of quick tasks before the week fills up.
Common questions
How do founders prioritize when everything feels urgent?
Set explicit criteria first. Work that brings in customers, cash or learning comes first; work that only makes things smoother waits. Then check your real bandwidth, delegate what others can do with a clear outcome, and accept “good enough” on the rest.
How do I turn a vision into a plan my team can execute?
Get the vision onto paper, rewrite it as concrete user stories, and group the simplest ones into an MVP. Then use the five questions to decide what changes, what it requires and what starts first, so the team has one clear next step.
What is the difference between urgent and important?
Urgent work has a deadline that someone will notice. Important work moves you toward your goals. In an early-stage company the two overlap more than usual, which is why it helps to judge every task by one question: does it help the company survive and learn?
Want help putting this into practice?
These methods are simple to describe and hard to apply alone, especially when you are in the middle of the wave. This is much of the work I do in founder coaching and tech leadership coaching. The first call is free, and we will look at what is on your plate right now.
