Building digital solutions that are useful, usable, sustainable, and governable — in the environments where they actually operate.
Successful digital solutions require more than great code or clever product ideas. In organizations with large, complex, and critical systems, success depends on aligning technology with organizational goals, stakeholder and user needs, and the real-world constraints that shape what is possible — time, budget, compliance, data quality, legacy systems, and operating realities.
This book gives you practical approaches to manage that complexity — whether you're improving an internal service or process, implementing a cross-functional enterprise information system, or building a new product or feature. You will learn how to work with stakeholders to design and implement solutions that are useful, usable, sustainable, and governable in the environments where they operate.
What You Will Learn
1
Understand and navigate complex stakeholder needs and constraints
2
Design products and information systems that fit their organizational and technical ecosystems
3
Clarify goals and outcomes, then translate them into actionable requirements and backlogs
4
Make informed trade-offs when priorities compete and information is incomplete
5
Plan and deliver iteratively in value-driven ways
6
Operate, measure, and improve solutions over time based on real usage and feedback
7
Incorporate sustainability, responsible AI, and "avoid harm" considerations into decisions from discovery through delivery
Foundation
Ideas That Inform This Book
This book is grounded in four core ideas that shape how we define, build, and evolve digital solutions.
01
Digital solutions are sociotechnical systems and services
Software and information systems don't create value on their own. They create value when they support people's work, decision-making, and coordination — inside real processes, cultures, policies, and constraints. Even when you're "building a product," you're ultimately delivering a service: something people rely on, interpret, and adapt to over time.
02
We take a goal-oriented, human-centered approach
The point of development isn't output (features shipped). It's outcomes — problems solved, value created, risk reduced. That means starting with goals and user needs, then designing solutions that work for real people in real contexts, while balancing organizational objectives, constraints, and long-term viability.
03
We take a participatory design approach
The people who will use and be affected by a system should have a meaningful role in shaping it. Participatory design strengthens understanding of real needs and work practices, surfaces hidden constraints, improves adoption, and reduces the risk of building solutions that look good on paper but fail in practice. Throughout this book, you'll learn concrete ways to engage stakeholders and users as partners — not just as "requirements sources."
04
We design for sustainability and responsibility
Every solution must be feasible to build, operate, support, and evolve over time. But feasibility alone isn't enough. We also consider environmental impact — resource use, compute, storage, energy, and hardware lifecycles — and social responsibility, ensuring solutions don't create preventable negative impacts such as inequity, exclusion, undue surveillance, or unsafe outcomes. As AI becomes embedded in more products and systems, these considerations become more urgent: algorithmic decisions can scale bias and harm as easily as they scale efficiency. Responsible AI practices are not an afterthought — they are woven into how we define requirements, evaluate design choices, and measure success.
These considerations are not "extra requirements" to add at the end. They shape goals, constraints, design choices, and how we evaluate success.
Systems Thinking
Understanding Complex Systems
Modern digital solutions are built and delivered within sociotechnical systems that combine people, processes, technology, and information. Systems thinking helps us look beyond isolated problems and consider the broader context — patterns, feedback loops, dependencies, and incentives that shape how systems behave over time. It helps teams identify unintended consequences, surface assumptions, and understand how changes in one part of the system ripple across others.
Fig 0.1 — The sociotechnical ecosystem: five interacting elements
Technology.Software, hardware, networks, platforms, and databases that enable and constrain work
People.Employees, customers, partners, and other stakeholders with goals, incentives, relationships, and cultures
Processes.How work and information flow across teams and organizations, including policies and governance
Information & Data.The inputs that shape decisions, automation, and accountability — including quality and access
The Delivery Team.How a team is structured directly shapes what gets built and how reliably value is delivered. Teams that inspect and adapt how they work tend to learn faster, manage risk better, and deliver more predictably
So how do we make sense of this complexity? More importantly, how do we ensure the solutions we implement meet the needs of the organization and the people it serves — while avoiding preventable harm? We use a set of practices that help you clarify outcomes, engage stakeholders meaningfully, learn early, coordinate work, manage risk, and improve continuously — while keeping sustainability and the broader system impacts in view.
This book takes a holistic view — one in which we design solutions that are aligned to organizational goals, usable by stakeholders, and sustainable to operate and improve over time.
Book Structure
How This Book Is Organized
We follow a three-part structure that mirrors the process teams use to implement solutions — from understanding the opportunity through the design, development, and delivery of the final solution.
Chapters 1–3
Part I: Core Practices & Tools
Introduces the foundational practices and tools you'll use to plan and deliver a product or information management solution. You'll learn how modern teams structure their work, how to identify and collaborate with stakeholders, and how to use discovery methods and artifacts to uncover goals, needs, and requirements.
Chapters 4–8
Part II: Defining Goals & Needs
Goes deeper into how to define the goals and requirements that shape your solution. You'll learn how to translate discovery insights into clear outcomes, user needs, system and AI requirements, and a backlog your team can actually implement.
Chapters 9–11
Part III: Deliver & Improve
Focuses on turning goals and requirements into working solutions and improving them over time. You'll learn how to plan and run iterations, deploy and operate systems reliably, and use data and feedback to drive continuous improvement.
A Note on Terminology
Throughout this book, we use the terms system, product, application, and solution broadly to refer to digital capabilities delivered through software and information systems — whether you're building internal tools, client-facing applications, commercial products, or integrated platforms. When distinctions matter (for example, product vs. service, or system vs. component), we'll make them explicit.