No One Ever Asked You to Think That Big

One of our most engaged beta users runs a one-person nonprofit. She is the program staff, the development office, and the communications team, and this spring she became the finance department too. She is very good at her job. More precisely, she is very good at the twelve jobs stacked inside her job.

Recently we walked her through a bigger way of seeing her organization: not the tasks in front of her, not the fire closest to her feet, but where the whole thing is trying to go. She tracked every step. She asked sharp questions. She could follow the logic as soon as there was room to lay it out. And somewhere in that conversation, it became clear that in all her years running this organization, no one had ever asked her to think that big.

Not her board. Not a funder. No one.

The Leader Did Not Need More Information. She Needed Altitude.

When we started building, we assumed the problem was storage. Leaders had good instincts, good work, good knowledge, they just needed somewhere to keep it all.

But something shifted when we walked her through a bigger way of seeing her organization. It wasn't that she couldn't hold the information. It was that she had never been asked to step back far enough to see the shape of it.

She didn't need a better filing system. She needed altitude.

Over the past year and a half, through discovery calls, demos, long listening sessions, and now the beta, the same pattern has kept surfacing. Most mission-driven leaders live in the daily crush, what's in front of me right now, what's due Friday, which fire is closest. They operate at the bottom of a hierarchy that looks like this:

• Mission (the North Star)
• Strategy (the long-term direction)
• Objectives (what needs to happen)
• Initiatives (the work)
• Projects (the components)
• Tasks (the daily reality)

Almost nothing connects those levels to each other. A leader at the bottom rarely gets to see where the daily decisions connect to the strategy, or where the strategy connects to the mission. Most board committees stay at the top. Almost nothing bridges them. That disconnection is not a memory problem. It is a hierarchy problem, and before that, an invitation problem. Someone has to ask the right questions long enough for the organization to see itself whole.

The Lazy Diagnosis Is Discipline. The Real Diagnosis Is Disconnection.

The sector mostly treats this as a discipline problem. Organizations need to be more strategic. Every funder asks for the strategic plan. The implication is quiet but clear: if you were more rigorous, you would have one.

I no longer believe that. I have watched too many capable people reason beautifully about big-picture thinking the moment someone walks them into it. The thinking is not missing. The knowledge is not missing either, it lives in board meetings, donor conversations, program notes, patient stories. But that knowledge lives in motion. It exists in inboxes and instinct, in the next urgent thing.

What was missing was not intelligence or discipline. It was a way to bring all of that knowledge into relationship with each other. A system that reasons over what the organization knows, not just preserves it. That connects the pieces and asks: does this move us toward our mission? Does this align with our objectives? What should we do next and why?

Readiness Begins Before the Opportunity Arrives

This matters because readiness is starting to matter more. By readiness I mean the ability to explain where the work is going before someone asks: what you are building, why now, what would change with more support, what evidence tells you it's worth doing.

Larger organizations often have language for those questions already. They have planning infrastructure, development support, board committees, consultants. But many of the people doing the most direct good in their communities have not been given that same chance. Nobody asked them to think big, and for a long time the penalty was easy to miss.

That is changing. Some funders are moving faster. Some are making larger, more flexible gifts. Some are doing their own research long before an organization ever knows it is being considered. In that environment, readiness is not just internal planning, it is what allows good work to be recognized when opportunity comes near it.

More than one leader has told us they stepped away from institutional funding years ago, having concluded the market was never built for organizations like theirs. Not because the work lacked value, but because the process required a readiness they were never resourced to build.

When the ask finally comes, the hierarchy gap becomes an opportunity gap.

The System Should Answer the Questions the Work Creates.

Here is the hopeful part: every organization already contains evidence. The board update that required three conversations to get right. The grant narrative that took weeks to shape. The donor conversation that surfaced a new possibility. The patient story that changed how the team saw the problem. The program note that revealed something that wasn't working. The half-formed idea after a hard meeting.

These are not separate pieces of work. They are evidence. They are reasoning. They are strategy before it has been organized.

The question is not whether the work contains strategy. The question is whether there is a system to recognize it when it appears, organize it while it's emerging, and reason over it in the context of what the organization is actually trying to accomplish.

An operating system for mission work would do something different than simply archive what leaders already know. It would help them:

• See where today's decisions connect to tomorrow's direction
• Recognize which work advances their mission and which work doesn't
• Make sense of what they've learned and what it means for what comes next
• Explain their strategy before someone asks, because it's visible to them first

The strategy lives there already, half built, inside the work they were already doing. They did not need to become a different kind of leader. They needed a system that could help them gather, recognize, organize, and reason over the knowledge already moving through the work. A system that continuously asks: what does this tell us about what we're trying to do?

No One Ever Asks, But Once Someone Does, They Can.

Readiness does not start with a planning retreat. It starts with someone asking a bigger question: What is this work trying to accomplish? Where are we headed? What would change if we had more support?

The solo leader did not need a consultant. She needed someone to ask. And once they did, she could. She tracked every step. She asked sharp questions. She could follow the logic.

That is the part we should not miss.

If the big thinking has always felt like someone else's job, that is not a flaw in you. It may be an invitation gap. It may be a hierarchy that was never made visible. It may be that the system around you was never designed to help you see the shape of your own work.

Consider this the ask: not for a finished strategic plan, but for a little room to look beyond Friday. To see where the work is trying to go. To understand what evidence is already in your hands about whether you're moving toward what matters most.

That is when readiness begins.