Beyond the Order-Taker: Rediscovering the Heart of Business Analysis
How a business analysis community of practice helped a team move beyond technical requests and rediscover the business problems worth solving.
Read article →Writing by Johanne Cannon
Articles on asking better questions, building strategy, and turning analysis into meaningful change. Browse six themes below, or follow one of four reading series.
Series 1 connects strategic discovery, prioritization, and operating models. The other series explore business analysis techniques, leadership, and AI.
How a business analysis community of practice helped a team move beyond technical requests and rediscover the business problems worth solving.
Read article →Distinguish an ambition from a business problem, then use evidence and better questions to uncover what needs to change.
Read article →Use a simple pyramid to visualize the main components of a problem or program and identify the owners responsible for coordinating the work.
Read article →Choose which validated problem to tackle first, make trade-offs explicit, and give your teams room to focus.
Read article →Test the assumptions behind a proposed strategy before committing time, money, or people to the wrong solution.
Read article →Connect a shared purpose to a primary measure, with guardrails that protect quality, people, and responsible decision-making.
Read article →Turn a shared ambition into action through clear requirements, decision authority, coordinated work, and small tests that help teams learn.
Read article →Look beyond reporting lines and challenge assumptions about managers, decision authority, specialist coaching, and generalists to design how work delivers value.
Read article →Map the capabilities that set direction, create customer value, and support delivery across the organization.
Read article →Use practical questions about ownership, technology, and delivery to uncover opportunities for a more connected operating model.
Read article →An illustrative mortgage-onboarding example shows how shared ownership could reduce handoffs, with outcomes to test rather than assume.
Read article →Reflect on the role of business analysis in strategy, the value of facilitation, and the importance of respectful challenge.
Read article →Explore four practical disciplines: root cause analysis, current-state analysis, business requirements, and solution analysis.
Read article →Recognize when a request for software is masking an undefined business problem, and establish a better starting point.
Read article →Follow an illustrative CRM conversation to uncover manual work, gaps in ownership, and the need to standardize processes.
Read article →Use an illustrative sales process to quantify wasted effort and assess exposure before choosing how to improve it.
Read article →Define the outcome the business needs, establish measurable acceptance criteria, and keep possible solutions open.
Read article →Compare manual improvements, standard software, and customization in a facilitated discussion grounded in agreed requirements.
Read article →Follow a practical roadmap from problem discovery and strategic focus to requirements, solution choices, and shared action.
Read article →Explore how clarity, trust, and autonomy help leaders support people without needing to be the expert in every task.
Read article →Connect executive direction, management priorities, team expertise, and feedback to turn a shared vision into action.
Read article →Bring operational knowledge into strategic planning so teams can shape the response and challenge assumptions early.
Read article →Organize related work around business outcomes, using projects where useful and ongoing learning to keep strategy connected to delivery.
Read article →Turn an evidence-based problem statement into a program with clear outcomes, measures, ownership, and regular learning.
Read article →Build AI capability around the people who know your business, adding specialist expertise where it addresses a clear need.
Read article →Make room for learning, agree responsible boundaries, and shape an AI strategy that draws on your people’s knowledge.
Read article →A plain-language introduction to models, connectors, and agents, with a client follow-up example and practical questions about where information goes.
Read article →Problem-to-program worksheet: a printable guide for a team conversation about evidence, outcomes, ownership, and next steps.