Our lead software engineer says their work is too creative and research-heavy to fit into a weekly scorecard. How do we use the Great Day or Lousy Day framework to find objective measurables for a highly technical role?

Question

Tyler Smith · Accepted Answer

The argument that technical or creative work cannot be measured is a common defense mechanism, but it is incorrect. Every role in your organization exists to produce an outcome. To break through this resistance, sit down with your lead software engineer and a blank legal pad. Draw a line down the middle, writing "Great Day" on one side and "Lousy Day" on the other.

Ask them to describe what happens on a great day in the engineering department. They might say they write clean code, merge pull requests without breaking the main branch, and unblock junior developers. On a lousy day, they spend hours fixing bugs, deal with system outages, and miss product release deadlines.

Now, convert these descriptions into weekly quantitative metrics.

- A great day of writing clean code becomes the percentage of code reviews completed within twenty-four hours.
- Unblocking junior developers becomes the weekly number of open pull requests waiting for review.
- Preventing bugs becomes the number of critical bugs found in production.

By translating their qualitative experiences into measurable activities, you create a scorecard that reflects their actual workload while giving the leadership team clear visibility into engineering throughput. This ensures your technical operations are predictable and accountable.