Leading in the AI Era Module 2 · Lesson 2.4 · Rethinking time, cost and capability

What the team needs to deliver

Updated

Beginner

What you'll learn

~8 min
  • Name the three things a team needs to deliver: domain knowledge, access and review capacity
  • Compare what a small team can prototype with what the organization must supply
  • Ask a team for a one-line capacity statement before a prototype becomes a service

You leave this lesson with: a one-line capacity statement for the team: what it can prototype, and what the organization must still supply.

Why a small team can demonstrate quickly

A university research group wants a tool that sorts instrument logs and flags runs that look wrong. Scientists in the group, who know what a bad run looks like, build a working version with AI tools.

This illustration shows a possibility to test, not an observed delivery result. People who know the work can try an idea without waiting in a queue for a developer. What they need is plain: domain knowledge to describe the task and recognize errors, access to the data and tools, and someone to check the output.

Domain experts can test whether AI tools help them produce a working prototype sooner. The developer trials in Lesson 2.2, which timed individual tasks, do not establish a general reduction in time to prototype, or show that smaller teams can maintain, secure and operate production systems with fewer people.

What the team needs to deliver

Ask three questions of any team that says it can deliver.

Domain knowledge. Who knows what a correct answer looks like? The scientists did. A tool that is built quickly by people who cannot tell a right answer from a wrong one is a risk, not an asset.

Access. Can the team reach the data and the tools it needs, within the organization’s data rules? Access review protects data and systems, and a prototype built on invented data proves little. If a request waits, record the waiting time and the queue’s owner (Lesson 3.1: unowned queues are where time goes).

Review capacity. Who reads the output, the code and the data handling, and how many days does that take? Review protects the people whose data and decisions are involved. The leader’s question is whether someone is assigned to do it.

Treat review capacity as a calendar question. Name who reviews, how many working days the review takes, and what else those reviewers are already reviewing. A reviewer with a full queue cannot take on a prototype without something else waiting, so the useful decision is which review comes first and who sets that order.

What the organization still supplies

A prototype is not yet a service: a system staff rely on every day, with a named owner who fixes it when it fails (Lesson 2.3 sets the two side by side).

Work demonstratedNamed capacity still needed
BuildA working first versionMaintenance when staff change or the tool is updated
SafetyA check on a sampleSecurity and privacy review matched to the consequence
ConnectionA standalone demoIntegration with the systems people use
RunningOne person keeps it goingSupport, monitoring and a named owner

Ask for each row of the table in the team’s own words, with a name beside it. A row without a name is a task nobody has been given, and it is the one that stalls the service after the demonstration succeeds.

When a team says it can deliver with fewer people, ask what the claim rests on. A prototype shows the build. It does not show who will answer user questions, who will update the tool when the data changes, or who will review each change. Put those three into the capacity statement, and mark any that are not yet known as not yet known.

💡Write the capacity statement

Ask the team to finish this sentence: “We can prototype X in Y days. To run it, the organization needs Z people for review, integration and support.” If Z is blank, the plan is incomplete.

KNOWLEDGE CHECK

A team of domain experts presents a working prototype. What may a leader reasonably conclude?

Optional deeper reading: Operating in Production leadership brief, one page

Key takeaway

LEADERSHIP DECISION
Name who supplies review, integration and operating capacity before a prototype is promoted to a service.
IMMEDIATE ACTION
Ask the team to write the capacity statement: what it can prototype, and what the organization must supply to run it.
SUCCESS MEASURE
Calendar days between a finished prototype and a completed review, against the team's own record for the last comparable change.
Search lessons