# Outputs vs Outcomes in Software Engineering

As a software engineer, understanding the difference between outputs and outcomes is crucial for delivering real value. In simple terms, *outputs* are just the things we build, and *outcomes* are why we build them.

### **Outputs**

When we build software, outputs are the actual stuff we create and can see right away.  
***Outputs*** => the tangible stuff we build.  
**Example:**  
New user sign-up form  
PDF Export  
How many bugs closed

### **Outcomes**

Outcomes are different - they show how our work actually helped the business or made users happy.  
***Outcomes*** => The actual value outputs created  
**Example**:  
More users are signing up for your product  
Increasing revenue  
Getting fewer help desk tickets  
Positive feedback from customer

### **Conclusion**

**Outputs**: We added a feature that suggests search terms as you type.  
**Outcomes**: People found what they wanted 40% faster and fewer people gave up before buying