Founders ask Collective 54 this once in our records, and that was in 2026. The prompts, workflow mapping and AI agent answers on this site cover writing instructions and redesigning workflows; this page covers using AI as a thinking partner on a single problem.
The delivery professional essay in the newer book lists what AI assistants now do for the person doing the work. They remove the blank page, producing first drafts, multiple structures and alternative narratives instantly. They make synthesis cheap, turning interviews into requirements, meetings into decisions and research into insight. They multiply analysis, cleaning messy inputs, validating assumptions, running scenarios and comparing alternatives. And they make iteration nearly free, so the person stops building each version by hand and starts curating.
The essay is careful about the limit. AI can produce content; it cannot produce accountability. Clients pay for credible outcomes from someone who owns what is true, what is right and what is safe to act on. As an inference, that is the right frame for any thinking tool. It is very good at showing you ways to see a problem. It is not responsible for which way you choose.
The prompts answer on this site says the quality of AI output depends on how much of the judgment and proprietary context of the firm went into the instruction, and that a generic request fails because it gives the model nothing a competitor could not also give it. The essay begins its walk-through the same way: AI summarizes notes, interviews, prior work and discovery calls into a clean brief, and a person confirms what is true, what is relevant and what the client actually needs.
As an inference, start by giving the tool everything you know: the situation, the goal, the constraints, what has been tried, and who decides. Ask it to restate the problem in a few sentences and list what it does not know. Correct the restatement before going further. Most bad plans come from solving the wrong problem well.
The essay describes AI generating multiple outlines and narrative arcs, and says the person chooses the arc and sets the thesis. As an inference, ask for three or four different ways to break the problem down, for example by cause, by stakeholder, by stage or by option, each with the question it would answer first. Seeing several framings side by side is where the speed comes from. You notice the one that fits your situation faster than you would have built any of them.
As an inference, pick one framing, or combine two, and write down in a sentence why. That sentence is your thesis, and it is the part of the work that belongs to you. If you cannot say why one framing is better, the tool has not failed; you do not yet understand the problem well enough, and the next step is to gather more information rather than more options.
The essay describes AI helping define good enough in concrete terms: creating acceptance criteria, suggesting a definition of done, generating a version one and version two plan, and proposing time-boxed options. As an inference, ask the tool to turn your chosen breakdown into a sequence of steps, each with an owner, an output and a test for when it is finished, and to mark the steps that depend on decisions only a person can make. The workflow mapping answer on this site uses the same discipline at the level of a whole workflow.
The essay says AI agents can validate assumptions, flag inconsistencies, run scenarios and sensitivity checks, and surface tradeoffs, and that continuous quality checks catch contradictions, missing support and weak logic. As an inference, before you commit, ask the tool to attack its own plan: what assumptions it rests on, what would make it fail, which step is most likely to slip, and what a skeptical client or partner would object to. Then ask for the cheapest way to test the riskiest assumption first.
The essay distinguishes assistants, which work alongside you in the moment, from agents, which execute tasks end to end with checkpoints and return work for review. It says agents allow real parallel work inside one workstream: while the person refines the storyline and manages stakeholders, agents draft appendices, build supporting analysis and compile evidence. As an inference, once the plan exists, mark which steps an agent could run and which need you, and hand off the first kind with a clear output and a checkpoint. The AI agent answer on this site covers building those.
The essay lists what the person owns in the 80 and 20 model: judgment, truth, taste, risk awareness, stakeholder intuition and responsibility. As an inference, in problem solving that means four things the tool should not decide for you: which problem is worth solving, which framing fits this client, which risks are acceptable, and when the plan is good enough to act on. A plan that reads well is not the same as a plan that is right, and only the person who will answer for it can tell the difference.
The essay says AI makes new kinds of deliverables affordable, including diagnostic tools that increase clarity and simulations that de-risk decisions, and describes surprise and delight as something that becomes realistic. As an inference, breaking a problem down with the client, generating options live and choosing together, can turn a planning session into a visible demonstration of how the firm thinks. Prepare the context in advance and keep the choosing with the people in the room.
The essay says AI assistants can turn project artifacts into reusable templates, checklists and playbooks, and that this is how a boutique firm becomes a scalable one. As an inference, when a breakdown works well for a type of problem, save the framing and the instruction that produced it so the next person starts from it. The prompts answer on this site covers keeping that library owned and current.
Collective 54 recommends no specific AI tool, model or problem-solving framework. The published positions are AI removing the blank page and producing multiple structures, thinking with something in front of you being faster, cheap synthesis and analysis, near-free iteration and curating rather than building, the 80 and 20 division of labor, AI producing content but not accountability, the human confirming what is true and choosing the storyline, definitions of done and version plans, assumption checks and scenarios, assistants versus agents and parallel work, new deliverables such as diagnostics, and capturing reusable assets.
If the problem is sensitive client information, as an inference, check your data rules before putting it into any tool; the data protection answer on this site covers that.
If the problem is simple and familiar, skip the options step and go straight to a plan.
And if nobody will own the decision, no tool will help; settle who decides before you start.
Give the tool the real context and have it restate the problem. Ask for several different ways to break it down, choose one and write down why, then have it turn that choice into steps with owners, outputs and a definition of done. Ask it to attack its own plan, test the riskiest assumption first, hand suitable steps to agents with checkpoints, and keep the judgment, the choice and the accountability with a named person.
The delivery professional essay says AI can produce multiple structures and alternative narratives instantly. As an inference, use it to generate options and keep the choice for yourself.
As an inference, the situation, goal, constraints, what has been tried and who decides. The prompts answer on this site says output quality depends on the context you supply.
Not on its own. The essay says AI produces content but not accountability. As an inference, ask it to test its own assumptions, then decide yourself.
The essay says assistants work alongside you in the moment, while agents run tasks end to end with checkpoints and return work for review.
Sources: Greg Alexander, The AI-Native Boutique Firm (Advantage Books, January 2027), specifically The AI Delivery Professional for the blank page as a cost, multiple structures and alternative narratives, thinking with something in front of you, cheap synthesis, multiplied analysis, near-free iteration and curating, the 80 and 20 model, AI producing content but not accountability, the deliverable walk-through in which AI drafts and a person confirms what is true and chooses the storyline, acceptance criteria, definitions of done and version plans, assumption checks and scenarios, assistants versus agents and parallel work, new deliverables such as diagnostics and simulations, and turning artifacts into reusable assets. Related Collective 54 answers on this site: what is the best way to write and maintain effective AI prompts; what is the process for mapping our workflow so AI can turn it into a strategy; how do I actually design and build an AI agent or workflow for a task; how do we protect client and sensitive data when using AI tools. Note on scope: Collective 54 recommends no specific AI tool or problem-solving framework. The six steps, asking for several framings, writing down why, attacking the plan, testing the riskiest assumption, the four decisions that stay human, using it with a client and the flips are inferences used here to organize the source material rather than published Collective 54 positions.
Collective 54 is the private community for founders and executives of boutique professional services firms between $5M and $50M in revenue. Members work these answers against their own numbers.