Skip to main content

Input, Output and Outcome

August 6, 2019

Many years ago, I questioned myself about what makes a software product successful and what makes it fail. In project management, I observed that even if we deliver the project within budget, scope, and time, it still has the jeopardy to fail when launching into the market.

I continued to research and observe what is essential to make the product successful. I found that one of the reasons the success of a product is impacted is a weak connection between Input, Output, and Outcome. People are easy to focus too much on Output and focus less on Outcome or don't build a strong connection between Input, Output, and Outcome.


Definition of "Input," "Output," and "Outcome."

Input: Anything needed for project or product. In this context, it will be: Money, time estimated, resources, people, efforts, plans, documents... prepared for that project or product

Output: In terms of Project or Product will be: Features, Product, or Service can be used by users. (measurable)

Outcome: Feedback or feelings of the user when using the product or the features. (hard to be measured)


Input Output and Outcome


If we investigate deeper, when we invest Money, Resources, and Technology to a project, it is "Input”. Then the result of that investment is a product, or features meet with the initial requirement, on-time, and on budget - is "Output". In the next step, we deliver the product and features to market for the end-users to use. In this phase, the feedback and feelings of the users about the product or service is the "Outcome".


The broken line between Input, Output, and Outcome

Many people thought that the product would be a success if we had more features than the competitors. That is not entirely wrong. But the success of the product also needs to be realized from the other elements; such as whether the user is happy with the features of your product, or it makes them disappointed and go with your competitors, even your product has many features. In this case, you will lose the users and waste all the efforts to build the product.

This holds true especially if software development is in a complex environment, by “Technology”, "People" and "Market". Therefore, focus on increasing the number of features, or trying to gold plate the idea, looking for perfection, but not linking it with the market is a danger. It can lead you to build an outdated product or a thing users never need.

For that reason, let’s build the line to connect your product with the users, get the feedback about the product as soon as possible and frequently. It will help you collect the data and sight to continue to improve product values instead of spending all money, effort, and time to develop, then bring it to the market. It's just like a big gamble, where you play "All in" but the percent of winning is low.


Input Output and Outcome with Scrum



"Input", "Output" or "Outcome" are the same level of importance. If you forget one or do not have a connection between "Input", "Output", "Outcome", it will impact the success of your product. Therefore, build the circle with a strong connection between "Input", "Output", and "Outcome", to deliver the value to the user fast enough and frequently for the experiment, and learn from your users what is essential. That is the core of Scrum. Every Sprint (one month timebox), we have a Done Increment that is ready to send to the users. From that, we will receive feedback to improve our product in the next Sprint. Scrum creates a strong connection between "Input", "Output", and "Outcome".


What did you think about this post?