Skip to main content

What is the difference between Customer and End Users?

In a lot of IT projects, Customer and End User contains the same group of people, even if in realty they are different. Because of this, we can end up very easily into a conflict between different scopes.
In today post we will take a look about the Customer and the End User of an application. We will try to define and discover what the similitudes and difference are between them.
The simplest way to describe this two roles is:
  • Customer: relates to the development process
  • End User: relates to product and services
TIP: You should never be end-user-driven, otherwise the customer will look as a ‘not team player’ – heathen person.
End User consumes and needs services brought by the product that you develop. For them, the application itself and the services/features from it bring the real value. In general, the source of revenue for customer is the end user that pays for this product. And in the end this feeds also the development team.
We can see a Customer, as a middle man between End User and development team, because they are not the consumers. In the same time, they play a crucial role. You shouldn't imagine the Customer as an external company, but is important to not have the Customer concept in the development team. We should have different teams and people. If we have the same people/teams we should keep in mind what is the role of each of them.
A customer can be seen as the role that takes the risks. For example he can identify a market opportunity, a lack of specific service. In this case he will risk and invest money in it. In this situations, Customer interest will be around development costs and delivery time. As software developer, you would expect a Customer to have a high interest in the functionality also, but usually the interest is not at the same level as costs and delivery time.
Because of this, the Customer should be involved in all process improvements areas (like retrospectives). His interest around development is not as high as we may expect.
In conclusion, we could say that customer is oriented to delivery, costs and processes. End User is oriented to application and what features are offered to resolve their problem (need). Knowing exactly who ‘plays’ the role of Customer and End User, we (as development team) can know exactly to witch role address different questions.

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...