The Senior Developer Is a Lookup Table

Illustrative scenario. Records, events and arithmetic are constructed examples, not findings about a named organisation.

At 16:42, a developer pastes service_ref: 008731 into Slack. The CMS export contains an identifier, a display name and a publication flag. The booking platform expects another key. The launch sheet records both systems as complete.

Three people know what the number means. One is on leave.

The technical director retrieves a spreadsheet from an old delivery channel. The developer copies the booking key. Testing resumes. No defect is logged.

The client has changed departments twice. Its catalogue contains names supplied by legal, names used by customers and names retained because an integration expects them. Some labels describe the same service. Others conceal different eligibility rules.

Across three account managers, two suppliers and a procurement process that priced delivery before anyone inspected the source data, the technical director has preserved distinctions that the specifications never recorded and the acceptance tests never required anyone to prove.

That knowledge is real work.

You can understand the impatience with another dashboard. The team has attended the workshop and watched unanswered questions move between project boards. The identifier remains 008731.

A meeting can assign the question. It cannot preserve the answer. Asking the director is rational when a release is approaching and the person who knows is available.

You have sat through this.

Model twelve people making five checks daily, with eight minutes spent searching, asking and applying each answer. Exclude the respondent’s time. Sixty checks consume eight staff-hours a day.

Across 220 working days, that is 1,760 hours. At an assumed loaded cost of A$100 per hour, the annual total is A$176,000. These are illustrative inputs; a fortnight of recorded checks would replace them.

The timesheet has room.

Some checks become implementation. Others become QA. The director’s contribution disappears into overhead. As the agency adds staff, more people need directions to the people who remember.

Outside parties deserve blame. The client renamed the service without funding the integration change. The vendor omitted the mapping. Procurement excluded discovery and requested certainty.

The change log supports the complaint. When the missing relationship surfaced, the agency could stop publication, reopen commercial discussions or ask the person who knew. That afternoon, asking may have been correct.

The inherited constraint explains the first lookup.

No.

Your senior team supplies the keys that your data model lacks.

The service needs an identity that survives a label change. Its booking relationship needs a maintained mapping and an owner. Release checks need to flag missing links before somebody asks Slack what a number means.

Senior judgement still matters. Once a decision is made, it must become maintained data. Instead, it becomes a successful conversation.

At 16:42 tomorrow, the agency will need the same person again.