The Investigator's Burden
What it costs to think deeply in a market that rewards speed — and how to carry it without breaking the business
I am an Enneagram Type 5. The Investigator. The defining drive is understanding — not just knowing, but comprehending fully, from first principles, before acting. The defining anxiety is incompetence, appearing uninformed, being exposed as someone who spoke before they knew.
This profile produces a particular kind of founder: someone who builds very slowly in the mind before moving quickly in the world. Someone who can map a system’s hidden constraints before a vendor meeting. Someone who tends toward mastery over visibility, depth over volume.
It also produces a particular set of failure modes. And running Futad for seven years in a market as fast-moving as Qatar forced me to develop a practice around managing them.
The Depth Trap
The most seductive failure mode for a depth-oriented founder is what I call the depth trap: the belief that more analysis will produce a better decision, past the point where additional analysis is actually improving the decision.
I have delayed client proposals by two weeks because I wanted to understand one more layer of their operational context. I have restructured a business plan three times because a new data point arrived that seemed to invalidate the previous model. I have stayed inside a strategic question long after the team needed a direction, not because I didn’t have an answer, but because I wasn’t certain it was the best one.
In each case, the cost of the delay exceeded the value of the additional clarity. That is the depth trap. It feels like rigour. It is often procrastination with better branding.
The depth trap feels like rigour. It is often procrastination with better branding.
The Information Hoarding Problem
Type 5 personalities tend to compartmentalise knowledge. To hold it close until they feel sufficiently confident in it. To be reluctant to delegate thinking before they’ve completed it themselves.
In a company with one person and no revenue, this is fine. In a company with a team, multiple divisions, and clients with live projects, it is a bottleneck. Not because the thinking is wrong, but because the team cannot execute on thinking they don’t have access to.
The discipline I’ve had to build — deliberately, against instinct — is what I’d call premature articulation. Sharing the incomplete model before I’m confident in it. Saying ‘this is where I am in the thinking, not where I’ve arrived’ — and trusting the team to hold the uncertainty without stalling.
This is harder than it sounds for someone whose identity is built around knowing before speaking. But it is the only way to lead a fast-moving organisation without becoming its ceiling.
The Solitude Requirement
Against these failure modes, the strength that makes the profile worth maintaining is the capacity for serious, undistracted analytical work. The ability to read a technical brief and see what’s missing. To sit with a problem for three days and produce a framework that the client hasn’t considered. To find the constraint that the vendor never disclosed because they didn’t know it existed.
That capacity requires solitude. Not occasional solitude — structured, defended, non-negotiable thinking time that the business is built around, not squeezed in between meetings.
I protect two to three hours per day where I am not available. Not for rest. For thought. The quality of every strategic decision I’ve made that I’m proud of traces back to time that was protected for thinking that had no immediate deliverable.
The best decisions I’ve made trace back to time that was protected for thinking with no immediate deliverable.
What This Means for How I Work With Clients
I share this not as autobiography but as operating context. Clients who work with me closely have observed a pattern: the initial engagement is slower than they expected. The questions are more probing. The first deliverable takes longer than the timeline suggested.
What follows is typically faster, more precise, and more durable than what they were expecting. Because the time spent on the front end — mapping constraints, asking the questions that weren’t in the brief, building the model from the ground up — compresses the back end significantly.
Understanding the profile helps calibrate the expectation. I am not a vendor who will execute your existing brief faster than the last one. I am a thinking partner who will help you determine whether the brief is correct before we execute anything.
The cost is time. The return is decisions you won’t have to make again.
More perspectives.
- Leadership · Founder mindset
Why culture is not a set of values on a wall, but a set of decisions made under pressure
You don't build culture through retreats and mission statements. You build it through the decisions you make in the moments when nobody would blame you for deciding differently.
- Founder mindset · Leadership · Strategy
Why I Call Myself a Builder-Philosopher — And Why That Label Matters
Build slowly. Think longer. Ship things that last.
- Founder mindset · Leadership
The Day I Realised I Wasn't Building a Company. I Was Building a Mirror.
There is a moment in every founder's journey that nobody prepares you for.