Category: Business Analysis

Business Analysis

General Business Analysis Blog Topic for BAs who want to Better themselves and advance their career

Business Analysis

From 5G to Smart Cities: How BAs Find Business Opportunities in Connected Data

Most people hear “5G” and think faster phone downloads. Business analysts should hear something different: a web of connected data and processes capable of transforming entire industries. In this episode of the Better Business Analyst Podcast, Benjamin Walsh unpacks what advanced connectivity — 5G, IoT, edge computing, and smart city technology — actually means for BAs, and how to find the real business opportunities hiding inside it. What Advanced Connectivity Actually Means for Business Here’s the technical picture, stripped of the buzzwords. 5G and 6G networks create ultra-low latency connections — data moves between devices, sensors, and systems in near real time. Pair that with IoT (billions of sensors and smart devices, many available for a few dollars on AliExpress) and you have live operational data everywhere. Add edge computing — which processes data locally rather than sending everything back to the cloud — and you get faster insights, lower costs, and new levels of automation. But here’s the BA translation: every sensor or device is part of a process. Every data point is a potential decision trigger. Every connected system creates an opportunity to add — or lose — value. The technology isn’t the story. The process change it enables is. Three Questions That Surface Every Connectivity Opportunity When Benjamin encounters new connectivity capabilities, he asks three questions to find where the real BA work is: Where does new data appear? — What sensors, systems, or connections are generating data that didn’t exist before? How does it change decisions? — Which decisions that used to be made manually, slowly, or with incomplete information can now be made faster or automated? What services, risks, or costs does it affect? — Where is the business impact — cost reduction, new revenue, risk mitigation, or improved customer experience? These three questions turn a technology trend into a BA engagement. The role of the BA is to map where connectivity meets the business — and that’s a process story, not a technical one. Real Examples: Where Connected Data Creates BA Opportunity Utilities and Energy: Smart Meters Smart meters and IoT sensors stream usage and fault data continuously. The opportunity: predictive maintenance (fix faults before they cause outages), dynamic pricing (charge more at peak times, less at off-peak), and customer transparency (show customers their real-time usage). A BA can define the data flows, map the changed processes, and qualify the business case — including the flip side: smart meters cost significant money to deploy and operate. Does the business case actually hold up once you model it properly? That’s a BA question, not a technical one. Local Government and Smart Cities Traffic sensors, GPS-tracked waste collection trucks, and connected street lighting all generate operational data. The opportunity: smarter truck routes (fewer kilometres, lower emissions, lower cost), faster fault detection (knowing when a streetlight fails before a resident reports it), and better traffic management. The BA connects that raw data to performance metrics and service delivery goals. This is process improvement at city scale — and it’s an area Benjamin is increasingly focused on. Healthcare: Wearables and Remote Monitoring Wearables, remote monitoring devices, and connected diagnostic tools shift healthcare from reactive to preventative — which is fundamentally a cost and outcomes story. For the BA, the work is analysing stakeholder needs (patients, clinicians, administrators), mapping patient journeys, and understanding the data dependencies between them. Security and privacy constraints are also key BA considerations in this space. The Core BA Insight: Sense, Decide, Act Faster When you strip away the technology jargon, what 5G and IoT actually deliver is the ability to sense, decide, and act faster. That’s a process story. The BA’s job is to identify which processes benefit most from that speed and visibility: Where are manual decisions slowing things down that could be automated or accelerated? Where can data remove guesswork or delay from a process step? Where can predictive analysis change when an action is taken — from reactive to preventative? These are the intersections where BA work lives: business process, technology capability, and customer value. That’s where BAs are most effective — and most needed. What This Means for BA Skills Data Literacy Is Now Core, Not Optional You don’t need to be a data scientist. But you do need to understand data flows, sources, latency, value, APIs, and where data is generated within a process. Benjamin has worked on data projects for two years and considers data literacy a foundational BA skill — not a specialisation. Process Modelling Must Evolve Traditional process models mapped human activities. Modern process models need to include digital actors too: sensors, bots, APIs, and events. A practical example from Benjamin: does that user need to fill in a form with their address, or does the mobile phone already know it? That’s an IoT-informed process decision — and it belongs in your process model. BAs Sit Between IT, Operations, and Strategy In a connected world, BAs need to connect business outcomes to network and data capabilities. That means collaborating with IT architects, operations leaders, and strategists — and representing the business perspective in conversations that can quickly become too technical. The skill is translation: turning connectivity into capability, sensor data into business decisions. Think Like a Value Designer Benjamin introduces the concept of “value engineering” — treating every connected device as an opportunity to measure and improve something, and every data stream as a potential fuel for a new service, a better customer experience, or a cost-saving initiative. The best BAs won’t just capture requirements in a connected world. They’ll translate connectivity into capability — turning streams of sensor data into smart decisions and better business outcomes. Three Questions to Start Using This Week Benjamin closes with three questions every BA should be asking right now, in any sector: What data do we already have that we’re not using to make better decisions? What data could we collect — or what’s coming — that we’re currently blind to? How can we turn that data into

Business Analysis

Going Deep with the 4P+ Framework: People, Processes, Projects, and Products

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. 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: Who are the people involved? — Who is affected, and how do they experience the current

Business Analysis

Bridging Strategy and Delivery: The Missing Middle Every BA Must Master

In this episode of the Better Business Analyst Podcast: Bridging Strategy and Delivery: The Missing BA Skill. Listen on Spotify or watch on YouTube. Episode Overview This episode covers practical business analysis concepts you can apply in your next project — whether you’re an experienced BA or just starting your career. Key Takeaways Practical techniques for real-world BA delivery How to apply these concepts across Agile and waterfall projects Examples from practising business analysts Listen to This Episode Available on Spotify and YouTube. Subscribe to the BA Podcast Weekly episodes on business analysis, requirements, stakeholder management, and BA career development. Subscribe on Spotify — or browse all episodes on our podcast page. Ready to Level Up? Explore our BA training courses — from free intro to CBBA certification. Join 2,000+ BAs who’ve trained with the Better Business Analysis Institute.

Business Analysis

Making Sense of Jira Goals: Connecting Your Work to Strategy

In this episode of the Better Business Analyst Podcast: Making Sense of Jira Goals — Connecting Work to Strategy. Listen on Spotify or watch on YouTube. Episode Overview This episode covers practical business analysis concepts you can apply in your next project — whether you’re an experienced BA or just starting your career. Key Takeaways Practical techniques for real-world BA delivery How to apply these concepts across Agile and waterfall projects Examples from practising business analysts Listen to This Episode Available on Spotify and YouTube. Subscribe to the BA Podcast Weekly episodes on business analysis, requirements, stakeholder management, and BA career development. Subscribe on Spotify — or browse all episodes on our podcast page. Ready to Level Up? Explore our BA training courses — from free intro to CBBA certification. Join 2,000+ BAs who’ve trained with the Better Business Analysis Institute.

Business Analysis

10 Things Every Business Analyst Should Know About Git and GitHub

In this episode of the Better Business Analyst Podcast: 10 Things Every BA Should Know About Git. Listen on Spotify or watch on YouTube. Episode Overview This episode covers practical business analysis concepts you can apply in your next project — whether you’re an experienced BA or just starting your career. Key Takeaways Practical techniques for real-world BA delivery How to apply these concepts across Agile and waterfall projects Examples from practising business analysts Listen to This Episode Available on Spotify and YouTube. Subscribe to the BA Podcast Weekly episodes on business analysis, requirements, stakeholder management, and BA career development. Subscribe on Spotify — or browse all episodes on our podcast page. Ready to Level Up? Explore our BA training courses — from free intro to CBBA certification. Join 2,000+ BAs who’ve trained with the Better Business Analysis Institute.

Business Analysis

Top 10 Job-Seeking Strategies for Business Analysts

In this episode of the Better Business Analyst Podcast: Top 10 Job-Seeking Strategies for Business Analysts. Listen on Spotify or watch on YouTube. Episode Overview This episode covers practical business analysis concepts you can apply in your next project — whether you’re an experienced BA or just starting your career. Key Takeaways Practical techniques for real-world BA delivery How to apply these concepts across Agile and waterfall projects Examples from practising business analysts Listen to This Episode Available on Spotify and YouTube. Subscribe to the BA Podcast Weekly episodes on business analysis, requirements, stakeholder management, and BA career development. Subscribe on Spotify — or browse all episodes on our podcast page. Ready to Level Up? Explore our BA training courses — from free intro to CBBA certification. Join 2,000+ BAs who’ve trained with the Better Business Analysis Institute.

Business Analysis

Continuous Discovery: How BAs Stay Connected to Real Customer Needs Throughout Delivery

In this episode of the Better Business Analyst Podcast: Continuous Discovery: The Best Way to Add BA Value. Listen on Spotify or watch on YouTube. Episode Overview This episode covers practical business analysis concepts you can apply in your next project — whether you’re an experienced BA or just starting your career. Key Takeaways Practical techniques for real-world BA delivery How to apply these concepts across Agile and waterfall projects Examples from practising business analysts Listen to This Episode Available on Spotify and YouTube. Subscribe to the BA Podcast Weekly episodes on business analysis, requirements, stakeholder management, and BA career development. Subscribe on Spotify — or browse all episodes on our podcast page. Ready to Level Up? Explore our BA training courses — from free intro to CBBA certification. Join 2,000+ BAs who’ve trained with the Better Business Analysis Institute.

Business Analysis

10 Ways Narrative and Storytelling Shape Better Business Analysis Outcomes

In this episode of the Better Business Analyst Podcast: 10 Ways Narrative Shapes Better Outcomes. Listen on Spotify or watch on YouTube. Episode Overview This episode covers practical business analysis concepts you can apply in your next project — whether you’re an experienced BA or just starting your career. Key Takeaways Practical techniques for real-world BA delivery How to apply these concepts across Agile and waterfall projects Examples from practising business analysts Listen to This Episode Available on Spotify and YouTube. Subscribe to the BA Podcast Weekly episodes on business analysis, requirements, stakeholder management, and BA career development. Subscribe on Spotify — or browse all episodes on our podcast page. Ready to Level Up? Explore our BA training courses — from free intro to CBBA certification. Join 2,000+ BAs who’ve trained with the Better Business Analysis Institute.

Agile, Business Analysis, Human Centered Design, Process to Requirement Thinking

The Number 1 Hack for Business Analysts – Process to Requirements Thinking (PTRT)

Are you a business analyst or agilest looking to enhance your requirements gathering skills? I highly recommend tuning in to the Better Business Analyst Podcast’s latest episode on “Process to Requirements Thinking (PTRT Modelling).” Process to Requirements thinking is a cutting-edge requirements elicitation model developed by The Better Business Analysis Institute (BBAI). This model empowers business analysts to apply scientific thinking to their requirements gathering process. 🧠💼 Built on the foundation of design thinking, user story mapping and UML, PTRT Modelling focuses on understanding the user’s desire to complete a job, commonly referred to as “a job to be done.” It provides a fresh perspective by viewing a job as a set of process steps from start to outcome, helping analysts gain deeper insights into user needs and expectations. 📈 We then model our requirements based on these process steps🔍 By listening to this podcast episode, you’ll gain invaluable knowledge and practical tips on how to leverage PTRT Modelling effectively. Tune in to the Better Business Analyst Podcast now and unlock the secrets of Process to Requirements Thinking. 🎙️🔓 #BusinessAnalysis #RequirementsGathering #PTRTModelling #BetterBusinessAnalystPodcast

The 4P+ Model
Agile, Business Analysis, Human Centered Design, Lean Start Up

The 4+ Model— Evolving Design Thinking, Lean Startup and Agile to include the Real World

I first drafted this article when I worked as a GM at Assurity Consulting with a large team who focused on different areas of IT change. The purpose of the 4P+ model was to show how the worlds of Human Centered Design, Business Analysis, Project and Product Management could come together to work as one when it come to Business Improvement. At The Better Business Analysis Institute we have built on this foundation with practical use cases that can be applied to complex projects. So what is the 4P+ Model…. https://medium.com/@bbainstitute/the-4-model-evolving-design-thinking-lean-startup-and-agile-to-include-the-real-world-ae87e3b2302b

Scroll to Top