E↗THE POWER OF THE EXPERTBY ROBYN MANCELL
Publish and productize

People Ask Me the Same Hard Question Every Week. Could I Turn My Answer Into Interactive Software? The Hidden Risk of Building Before the Answer Is Written Down

An expert mapping a decision process beside an interactive tool.

“You can only be in one room at a time. But your thinking doesn't have to be.”

— Robyn Mancell, The Power of the Expert, Chapter 10

Often, yes. A question people bring you every week is the best sign that your answer could become a tool, because the repetition shows a pattern and the stakes show it matters. The software does not replace you. It carries the first layer of your judgment to more people, so you can spend your time on the exceptions. But the tool can only be as good as the answer you write down first. Robyn Mancell, author of The Power of the Expert, names the limit it removes: "You can only be in one room at a time. But your thinking doesn't have to be." This article shows how to write the answer as a decision path, how AI can speed up building it, and where a tool built from your judgment must stop and hand off to you, followed by an action sequence you can start this week.

Why Is a Question People Ask Every Week a Good Candidate for Software?

Because repetition shows a pattern, and the pattern is what software can carry. If the same hard question keeps arriving, the answer probably follows a logic: what you ask first, what the answers suggest, and what you would recommend in each case. That logic is the valuable part, and it is already in your head.

There is evidence that carrying expert practice to more people can help. A study by Erik Brynjolfsson, Danielle Li, and Lindsey Raymond followed 5,172 customer-support agents who gained access to an AI assistant. Productivity rose by about 15 percent on average, with the largest gains for less experienced workers, and the researchers read the pattern as suggestive that the tool helped spread the practices of more able workers. That was a support setting, not your field, so treat it as a signal about scale, not a promise about your tool.

How Do I Choose Which Question to Start With?

Pick the question that arrives most often, carries stakes, and follows a logic. Mancell's filter for reading requests is that one that carries stakes and repeats is a vote for your judgment. Look for the question people ask after they have already tried the obvious answers, because that is where your experience adds the most. Then check that the answer follows a logic you can state. If every case needs a different kind of judgment, it is not yet ready for a tool. Start with one question, and do it well before you add a second.

What Do I Need to Write Down Before Anyone Builds Anything?

Your decision logic for that one question, in plain words. A tool cannot be built from a feeling. Before any developer or AI assistant touches it, write the answer as a path. Start with the question as a client would phrase it. Then list the things you always ask first, what each answer tells you, what you would recommend in each situation, and when you would say, "this needs a person."

Mancell's practice for turning judgment into something reusable is the same. Write down the questions you always ask before a major decision, note the mistakes you have made once and never want to make again, and turn hard-won lessons into a routine. The surgical checklist is a model: a short list of checks that catches what instinct can miss, even for expert surgeons.

How Can AI Help Build the Software, and What Is the Risk?

AI can speed up building, and it can be confidently wrong, so you must test what it produces. In a 2023 controlled experiment, Sida Peng and colleagues asked 95 professional developers to build an HTTP server in JavaScript. Those with access to GitHub Copilot finished about 56 percent faster than those without it. That is one coding task, so it shows the direction, not a guarantee.

The risk is just as documented. In a 2023 field experiment with 758 consultants, Fabrizio Dell'Acqua and colleagues gave some a task outside the AI's capability, and those using it were 19 percentage points less likely to reach the correct answer than those working without it. The tool sounded fluent and was wrong. That is why Mancell's rule applies to software as much as writing: never sign what you have not verified. Test the tool against real questions you already know the answers to, and check what matters most before anyone relies on it.

What Are the Limits of a Tool Built From My Judgment?

It carries your reasoning for common cases and cannot carry your accountability. Someone still has to sign. The Expert Edge Finder's terms say plainly that a proposed software concept should never be used as an operational medical, legal, financial, or safety-critical decision system without qualified review. If your field has those stakes, design the tool to hand off to you, and have it reviewed by someone qualified before anyone relies on it.

Design the hand-off on purpose. Decide which cases the tool answers, which it flags for your review, and which it declines. A good tool is honest about its edges, and the edges are where your judgment is most valuable. Keep your own voice in it, too. Write the questions and answers in the words you would use with a client, and a tool that sounds like you will earn the same trust you do.

What Does the Software Version of My Answer Look Like?

It handles the first layer of the question and sends the hard cases to you. The table compares answering by hand with answering through a tool, using only the ideas in this article.

Answering by hand, every weekCarrying the first layer in a tool
You answer the same question one person at a timeThe tool walks each person through your logic
Your time goes to the routine version of the questionYour time goes to the exceptions
Only people who can reach you benefitMore people reach your thinking
The logic lives in your headThe logic is written down and testable
Sample (illustrative): "Let me look at your situation on a call."Sample (illustrative): "Answer these six questions and see what I would check first, and when you need to talk to me."

How Do I Test Demand Before I Build?

Run a manual version first and see whether people use it. Before paying anyone to build software, offer the decision path as a simple form or a document and answer the results yourself. Count how many of the people who ask the weekly question would use it, and ask what they would want it to do. The Expert Edge Finder's guidance is to test any direction with someone who could benefit, and its profile offers three software concepts as ideas to consider, not as proof of demand. Real users are the only evidence of demand that counts.

Write the question exactly as the people who ask it phrase it.

Write your decision path: the first questions you ask, what each answer suggests, and what you would recommend.

Mark the hand-offs: the cases where the answer is, "this needs a person."

Test the path by hand with five people who ask the question. Note where they get stuck.

Bring the question and the path to the Expert Edge Finder at https://expertedgefinder.com/, a guided reflection with 12 questions that also proposes three distinct software concepts to consider as hypotheses to test.

What Does It Cost to Keep Answering the Same Question by Hand?

Each week you answer the same question for one person, your thinking reaches only the people you can fit in a room, and the logic stays unwritten while the question keeps coming. Written down, it can start working for you. Start at the Expert Edge Finder at https://expertedgefinder.com/.

Frequently Asked Questions

Could I turn my answer to a weekly question into interactive software?

Often, yes. A repeated hard question suggests a pattern. Write the answer as a decision path first, mark where it hands off to you, and test it by hand before anyone builds software.

Will the software replace me?

No. It carries the first layer of your reasoning to more people so you can spend time on the exceptions. Accountability still belongs to a person.

Isn't a tool like the Expert Edge Finder just suggesting software ideas I can't verify?

It offers three concepts as hypotheses, and it says so. The profile at https://expertedgefinder.com/ does not establish demand or promise revenue, and its terms say concepts should not be used as medical, legal, financial, or safety-critical decision systems without qualified review. Use it to organize your thinking, then test with real users.

Can AI build the tool for me?

AI can speed up building, as a 2023 experiment with 95 developers found, and it can be confidently wrong, as a 2023 study of consultants found. Test everything against questions you already know the answers to.

What if my field is regulated?

Then qualified review is part of the plan. Design the tool to hand off to a professional and have it reviewed before anyone relies on it.

Can this article tell me whether my idea will work?

No. It offers a framework and is not professional advice. Real users and real costs are the test.

References

Brynjolfsson, E., Li, D., & Raymond, L. R. (2025). Generative AI at work. Quarterly Journal of Economics, 140(2), 889–942. https://doi.org/10.1093/qje/qjae044

Peng, S., Kalliamvakou, E., Cihon, P., & Demirer, M. (2023). The impact of AI on developer productivity: Evidence from GitHub Copilot. arXiv:2302.06590. https://doi.org/10.48550/arXiv.2302.06590

Dell'Acqua, F., McFowland, E., Mollick, E., et al. (2023). Navigating the jagged technological frontier: Field experimental evidence of the effects of AI on knowledge worker productivity and quality. Harvard Business School Working Paper No. 24-013. https://doi.org/10.2139/ssrn.4573321

Haynes, A. B., Weiser, T. G., Berry, W. R., et al. (2009). A surgical safety checklist to reduce morbidity and mortality in a global population. New England Journal of Medicine, 360(5), 491–499. https://doi.org/10.1056/NEJMsa0810119

Mancell, R. (2026). The Power of the Expert: How to Become Irreplaceable in the Age of AI. https://www.amazon.com/dp/B0HNGTSPRX, Chapters 6 and 10

Expert Edge Finder. (2026, October 15). Terms and boundaries: Exploration, not verification. https://expertedgefinder.com/terms

Expert Edge Finder. (2026). Your possibilities: Your software ideas. https://expertedgefinder.com/

YOUR EXPERIENCE IS THE STARTING POINT

What could your expertise become?

Explore the problems people bring you, the judgment you have earned, and the possibilities ahead.

Try the free Expert Edge Finder ↗