There is a clear distinction between activity and impact, though we often use these terms interchangeably. The common assumption is that more activity will naturally lead to impact.
For example:
- We have executed 450 test cases;
- Written 500 lines of code;
- Called 4000 leads.
These are activities, but they may or may not result in impact.
On the other hand:
- We have ensured all critical business functions are working as expected;
- The integration between two systems is fully functional;
- We have received 10 inquiries.
These are examples of impact.
Setting expectations based on impact, and aligning our objectives with specific, measurable outcomes, makes far more sense. Taking pride solely in activity can lead to unnecessary noise and distraction.
