Demonstrate the Standard, Then Collect It

Description

When a new leadership expectation has to land across multiple orgs, Peter does not write a spec. He runs a live exemplar in public with the strongest performer first, says openly that the ordering was deliberate, keeps the form of the deliverable open so the ask stays about the thinking rather than the artifact, lets the delta be self-evident to the people who will have to close it, and then collects the same from everyone else on a named rotation. He prefers showing imperfect work now over polished work later.

Typical Approach

Pick the strongest performer and have them go first, then name it as intentional - it is not an accident that this person is going first here. Praise the thinking rather than the output: you are taking an opinion about what you want to see from your team and what you can measure to improve those outcomes. Leave the form deliberately open - I do not care whether there is a dashboard or just a system that reports a set of metrics - so nobody can satisfy the ask by copying the artifact. Say plainly that this is the kind of thing I am going to be looking for from every org. Propagate the exemplar sideways as a training artifact, including to peers outside engineering. Tell the person privately that the others will not measure up, so the bar is calibrated rather than implied. Put the remaining orgs on a dated rotation. Separately, ask for work in progress to be shown even if not perfect, because the visible rough state is what makes the structural problem legible to the whole room at once instead of in serial one-on-ones.

Trigger Conditions