Skip to main content

Before we build: Keeping product context that lasts

 When we build a digital solution, it is easy to move fast from an idea to implementation. A good prompt can help us create code or a specification, but it does not mean that we understand the business problem. Before we build, we need to understand who has the problem, how often it happens, what they do today, and what result would really matter.

Let’s use a simple example: invoice approval. At first, the request sounds clear: “We need to automate invoice approval.”

then…

  • But who submits the invoice?
  • Who checks the details?
  • Who is allowed to approve it?
  • What happens if the amount is above a limit, if the invoice is duplicated, or if some information is missing?
  • What if the approver is not available?

… and more …

These answers describe the real flow and the rules that give meaning to the solution. Without them, we may automate an incomplete process or improve one step that does not solve the main problem.

For this work, we need a way to keep the context. I think of it as a durable product context repository: an organised place where the team keeps information that can change a decision, a business rule, a priority, or a test. It does not mean documenting every conversation. It means keeping the evidence, business flows, rules, decisions, and open questions that a future team may need.

It is also important to know what type of information we have. A measurement from the system is an observed fact. “Approval takes two days” may be an estimate from a stakeholder. “Automation will remove the delays” is an assumption until we validate it. We should record the source and how sure we are about each statement. Later, we can check it again: is it still true? What evidence supports it? What have we learned that confirms or changes it?

This helps us choose what to learn first. Not all unknowns are equally important. A question should be investigated early when its answer can change what we build, or even our decision to continue.

Keeping this context becomes important when the product changes. In three or four years, the interface, database, or technology may be replaced. But the team should still understand who can approve an invoice, what must be audited, and which conditions must be met before payment. Code shows what the system does today. Business context explains what it needs to continue doing, and why.

Before we build, we should understand the problem, check what we know, and keep the reasons behind our decisions. This way, we can change the technology without losing the business logic that makes the solution valuable.

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...