Too many business analysts get stuck in the delivery weeds — writing requirements, managing backlogs, doing Jira admin — and forget the bigger picture. The 4P+ Framework is the mindset that changes that. In this episode of the Better Business Analyst Podcast, Benjamin Walsh goes deeper than ever into the model he’s developed over years of practice: People, Processes, Projects, and Products. Not as a theoretical framework, but as a practical way of seeing that separates high-value BAs from task-takers.

Listen on Spotify — The Better Business Analyst Podcast

Why the 4P+ Framework Matters More Than Any Methodology

You can know every Agile ceremony, every BABOK technique, and every Jira shortcut — and still be a low-value BA. The difference between a task-taker and a value creator isn’t technique. It’s how you see the world of business change.

The best analysts zoom out. They see how everything connects: the people using and shaping work, the processes that define how things run, the projects that drive change, and the products that deliver ongoing value. The 4P+ Framework is the lens that makes this possible.

P1: People — The Human Layer

Every process, every project, every product starts and ends with people. People follow processes. They deliver projects. They use products. If you don’t understand the people, you cannot design good systems or solutions — regardless of how well you document the technical requirements.

This is why personas, empathy maps, and stakeholder analysis aren’t “nice to have” tools. They’re essential. They uncover real needs and pain points — not by asking for them directly, but by extracting them. Benjamin makes a sharp distinction here: requirements elicitation (extracting requirements, pushing on areas, seeing which ones hurt) is fundamentally different from requirements gathering (writing a list of what stakeholders say they want).

A people analysis often reveals that the real problem isn’t what was assumed. Staff frustrated by an inconsistent process? It might not be a system issue — it might be a communication issue. Clients struggling with poor service? It might be frontline staff with different interpretations of the same process, not a technology gap. Start with people. Always.

P2: Processes — The Engine Room of Any Business

If people are the heart, processes are the engine. They define how work gets done today: the steps, decisions, and interactions that turn inputs into outputs — or ideally, outcomes.

Here’s a point Benjamin makes that surprises many BAs: current state analysis ideally shouldn’t need to be done. In a well-run business, processes are already documented at the capability level. Business architects and enterprise BAs know the high-level process landscape. When someone starts a project, they already know the box they’re playing in.

The reality? No one’s documented what they actually do. So BAs spend time on current state analysis — process mapping, swim lanes, BPMN — to visualise how things actually flow. Not how management thinks they flow. How real people do them.

The critical insight: processes exist before the project or product that’s changing them. They’re the source of the problems that justified the funding. Understanding them at capability level (value chains, business architecture) tells you where the real issues lie — and that’s the foundation everything else rests on.

P3: Projects — The Vehicles for Change

Projects are how organisations make change real. They exist to solve process problems and deliver improvements through products, services, or capabilities. But here’s where most BAs go wrong: they drop into projects halfway through, are expected to “get the requirements done,” and treat that as their primary job.

Your job isn’t to gather requirements. It’s to make sure the right change happens. That means understanding where the project sits in the wider organisation and strategy, who owns the change, and what success actually looks like — not just for the project, but for the process it’s meant to fix.

Benjamin shares a real example: a project scoped as “implement a new CRM” that turned out to be a data quality and process alignment problem. The team reframed it — running a CRM project and a change project in parallel — because the real problem wasn’t the tool. This kind of reframing is the BA’s most valuable contribution to a project, and it only happens when you understand the process layer first.

P4: Products — Delivering Value Beyond the Project

Projects end. Products live on. This is an important distinction, especially in organisations running lean startups or product management teams where “continuous improvement” can blur into endless delivery without strategic anchor.

In the world of product — whether a system, service, or internal tool — the product delivers ongoing value to the business and its customers. Products evolve, get feedback, get updates, and change shape over time. Modern BAs need to think like product analysts as well as project analysts.

The danger in pure product-team thinking: it can lose its purpose within the greater business capabilities and the people it ultimately serves. The product team becomes obsessed with its own users and metrics, disconnecting from the organisation’s strategic goals. The 4P+ model keeps the product layer anchored within the broader context of processes and people.

The Plus: The Feedback Loop

The model is cyclic. People using products generate insights that improve the next cycle of change. That’s the “+”. The feedback loop where real-world usage data flows back to inform better processes, better projects, and better products.

The four statements that hold it all together:

• People follow processes
• Projects aim to fix, enhance, or remove processes
• Projects deliver products
• Products create value for people

And the plus — the feedback loop — means people using the product generate insights that start the cycle again. This is why products are never truly “finished.” They’re the beginning of the next round of continuous improvement.

How to Apply the 4P+ Framework on Monday Morning

The next time you’re dropped into a project, use the 4P+ lens before you do anything else. Ask:

1. Who are the people involved? — Who is affected, and how do they experience the current situation?
2. What processes shape their experience? — Where does this fit within the organisation’s existing capabilities?
3. What project is delivering this change? — Or is this really a product iteration disguised as a project?
4. What product or outcome will deliver lasting value? — And what does “done” look like from a value perspective, not just a delivery perspective?

When you start seeing your work through this lens, everything shifts. You stop delivering outputs and start shaping outcomes. You stop gathering requirements and start guaranteeing value.

Key Takeaways

• The 4P+ Framework is a mindset, not just a model — it’s how high-value BAs see the world of business change
• People are the starting point for every process, project, and product — analyse them first, always
• Processes exist before the project. Understanding current-state capabilities tells you where the real problems lie
• A BA’s job in a project is to ensure the right change happens — not just to gather requirements
• Products deliver ongoing value beyond the project — modern BAs need to think like product analysts
• The feedback loop (the “+”) ensures product usage insights continuously improve the next cycle of change

Subscribe to the Podcast

New episodes of the Better Business Analyst Podcast drop weekly — covering BA frameworks, career development, Agile BA, and how to move from requirements gatherer to strategic value creator. Subscribe on Spotify or watch on YouTube.

Level Up Your BA Skills

If this episode resonated with you, our BA training courses teach the full 4P+ framework and how to apply it across the entire business analysis lifecycle. Also worth reading: What Is Business Analysis? | Business Analyst Career Path | Stakeholder Management for BAs