Operating Intelligence
Why We Ask What Breaks If You Take Two Weeks Off

“What breaks if you take two weeks off?”
We ask this question first because it makes the real gaps and weights of the business visible without forcing the owner into technical language. Conversations about tools and workflows starts with categories. The two-week question starts with the work that would stop, stall or come back wrong if the humans holding things together stepped away. It focuses on the real “system” in the business.
The question finds the weight
What we’ve found is that a business owner rarely arrives with a clean diagnosis. They arrive carrying weight and perhaps tired, irritated by repeated questions, worried about follow-up, or conscious that one client still needs them more than the process they share publicly tends to admit. The first job is not to sell an answer or a panacea, as tempting as it is to jump straight to relief. The first step is to find the weight accurately enough that the answer has somewhere real and valuable to land.
The question does that because it is concrete. It asks for a scene: you are gone for two weeks, the phone is off, and the business keeps running without private rescue. The answer names the quotes, approvals, relationships, spreadsheets and judgement calls that still depend on you.
It avoids feel good theatre
Questions about readiness often invite performance. People grade themselves against what they think a modern business should say. They talk about software, adoption, dashboards and process maturity. None of that tells you whether the business can keep a promise while the person carrying the context is away. That’s why we created our own free AI readiness assessment which focuses on what actually leads to success - not what feels like a nice pat on the back.
The two-week question is another thing that makes it harder for the respondent to perform. Either something would break, or it would not. If the honest answer is a list, the list becomes useful. This is the beginning of a map to a better and frankly more sustainable future state.
It matches how we think about work
The first meeting should be about questions, not a demo. You can’t pitch to something you don’t understand. Our founder has a postgraduate degree in design and believes on thing very strongly: you can only get the right answer by first solving the right problem. So that’s why starting with us means no pitch and no product at first. Just the answers to what breaks written down carefully enough that the owner can see the load they are carrying all in one place. From there, the work is to choose which piece can be lifted first based on what is going to give maximum relief and maximum ROI for the business. Has the vendor turning up around tools offered to work through that with you?
That is why the question matters. It is simple enough to answer, specific enough to make the hidden work visible, and respectful enough to start with the business the owner actually built.
It shows you what it’s like to work with us
The question also shows you what it is like to work with us. This simple question takes you to the place where time and energy leak and where business operators get stuck holding the system, and by extension the business, together through their own knowledge or effort. We’re proud to be able to identify ways to speak clearly and still get close to the business needs and places that will create the greatest ROI for you and your team. We hate jargon and you run a business, you don’t need a second job of trying to become and AI expert just to make things run better so you can take some more time away. It should always feel less like being sold technology and more like having a trusted adviser beside you.
That’s what we hope it’s like to work with us, and why we ask the 2 weeks question.
Do you want to step away for 2 weeks and know that nothing breaks? Book a call with Dean to discuss how we can help
Frequently asked
- What breaks if you take two weeks off?
- The answer shows which decisions, relationships, approvals, workarounds and client context still depend on one person.