Insights
What I see in projects, the questions they raise, and what I learn from them.
-
Business analysis
Why a clear requirements document saves time for the whole team, not just IT
A requirements document is often seen as a technical document, mainly intended for the team that will build the solution. In reality, it is first and foremost a tool for creating clarity. A clear requirements document helps business teams articulate what they need, the technical team understand what it has to build, and management weigh priorities before decisions become costly to change.
-
Business analysis
Choosing a CRM: 5 questions to ask before comparing tools
Comparing CRMs based on their features is a step that comes too early in most projects. Before opening a comparison table of tools, a few internal questions can clarify what the organisation actually expects from the future system. This helps avoid choosing a solution that does not fit the organisation's reality, however good it may look on paper.
-
Business analysis
What separates a good user story from a bad one, with concrete examples
The user story has become a common way of describing a need in a digital project. Its simple structure, "as a, I want, so that", hides a real difficulty. A user story can follow that structure perfectly while still leaving much of the need open to interpretation. The questions then surface during development, when decisions are more costly to change.