The two questions to ask yourself every week

Most dashboards are built to be looked at, not acted on. They show you a wall of charts, and you nod, and nothing changes. If you run something you care about, you do not need forty metrics every week. You need two questions answered honestly.

They are: how long have I got, and what should I build next? Almost every good decision you make falls out of those two. Almost every bad week comes from dodging one of them.

Question one: how long have I got?

This is your runway — how many months of cash you have left if nothing changes. It is the question that sets the stakes for everything else. A decision that is fine with twelve months of runway can be reckless with three.

The honest answer is a real number, computed from your actual cash and your actual costs — not a vibe, and not a figure you worked out in a spreadsheet two months ago and have quietly stopped believing. If you cannot say your runway out loud right now, that is the first thing to fix, because every other decision is being made in the dark.

You cannot decide what to build next until you know how much time you are deciding for.

Question two: what should I build next?

Once you know how long you have got, the next question is what to spend that time on. Not everything you could do — the one thing most worth doing next. This is where a long backlog actively hurts: a list of fifty "someday" items is a great way to avoid choosing.

The useful version of this question ties the work to the money. For each thing you are considering, you can ask: what will this cost me, and what should it bring in? A piece of work where you have answered both is what we call an initiative — work you have decided is worth doing, with an expected cost and what it should bring back. Framing it that way forces a real comparison instead of doing whatever is loudest.

You do not need a spreadsheet of net-present-value to do this. You need a rough, honest answer: this will take me two weeks and a contractor, and it should win back the client we lost, or unlock the feature three prospects asked for. That is enough to rank it against the other things competing for the same fortnight.

Why two beats forty

A big dashboard feels responsible, but it spreads your attention thin and rarely tells you what to do. Two questions concentrate it. They are also adversarial in a useful way: the runway question keeps you honest about time, and the build question keeps you honest about whether the work is worth it.

• They are quick. You can answer both in a few minutes, which means you will actually do it every week instead of "when things calm down".
• They connect. The first question sizes the budget of time; the second spends it. Neither makes sense alone.
• They are honest. Both have a right answer that you either know or do not — there is nowhere to hide behind a green chart.

Answering them without lying to yourself

The trap with both questions is the comfortable answer. Runway feels longer when you forget a cost; the next build feels obvious when it is just the fun one. The defence is the same for both: tie the answer to real numbers. Let your runway come from your actual cash and costs, and tie each candidate build to a real expected cost and return. When the numbers are in front of you, it is much harder to fool yourself.

This is the whole idea behind the Build Track in CentralHq: capture the ideas, turn the best ones into initiatives with a cost and an expected return, and ship them — with every cost and dollar tied back to the initiative, so you can see afterwards whether it paid off. Two questions, asked every week, answered with real numbers. See how the Build Track works, or start free and ask yourself both this Friday.