Diagnose Strengths, Gaps, and Aspirations

A growth diagnosis is a shared, evidence-based view of strengths, limiting gaps, aspirations, and available opportunity. Without it, managers assign generic “stretch work” and engineers collect activities that may not change capability or impact.

Diagnosis is not clinical language and does not label a person's fixed traits. It asks what behavior is reliable now, what constraint matters for a real next-scope outcome, and what experiment can produce better evidence.

Evidence describes an observable situation, behavior, and effect. Adjectives such as “strategic,” “executive,” or “not influential enough” hide what actually happened and make improvement difficult.

A reliable strength appears in more than one situation and produces useful effects. Name strengths precisely so the engineer can apply them deliberately rather than receiving empty praise.

Use these dimensions as prompts, adapted from themes in Monzo, Dropbox, and CircleCI frameworks:

A limiting gap is the one behavior or missing experience that constrains a valuable next-scope outcome. It is not every difference between the engineer and an idealized ladder profile.

For example, an engineer may write excellent architecture strategy but fail to involve the teams that must adopt it. The limiting gap is not “communication” in general; it may be early stakeholder discovery and shared decision design. That specificity suggests a practiceable experiment.

Separate three cases:

• Skill gap: the engineer has had a fair opportunity but the behavior is not reliable yet.
• Experience gap: the engineer has not encountered enough relevant situations to know.
• Opportunity gap: the organization has not provided access, mandate, or a real problem in which the behavior could be shown.

Managers must not describe an opportunity gap as personal deficiency.

Aspiration is the kind of contribution and working life the engineer wants, not merely the next title. Explore desired problems, people interaction, pace, depth, authority, and energy before choosing an assignment.

Engineer prompts:

• Which recent work made me curious enough to continue after the immediate task?
• Do I want enduring domain stewardship, coordinated execution, hard bounded problems, or broad strategy translation?
• Which costs am I willing to accept: longer feedback loops, more disagreement, less hands-on coding, or greater uncertainty?
• What do I not want my role to become?

Manager prompts:

• “Which parts of broader scope energize you, and which only look prestigious?”
• “What would a satisfying year look like even if the title did not change?”
• “Which archetype is a hypothesis worth testing, not an identity we must defend?”

Aspiration informs opportunity design but cannot promise a role the organization does not need. Say that plainly and early.

The course's synthesized diagnosis joins evidence, aspiration, need, and access. Each quadrant prevents a common mistake.

Disagreement is useful when both sides can test their models. Imagine Priya believes she is ready for broader scope, while her manager says she needs “more influence.”

Priya: “Can we replace influence with an observed situation and effect?”

Manager: “In the identity request for comments (RFC)—the written proposal used to gather feedback—two teams agreed in the room but did not adopt the decision. I did not see you learn their constraints before proposing it.”

Priya: “I agree adoption failed. I think the missing factor was authority: their directors had conflicting goals. Let us test both explanations.”

Joint experiment: Priya conducts discovery with engineers and directors, publishes conflicting incentives, creates shared decision criteria, and asks a neutral Staff engineer to observe. The evidence will distinguish a skill gap from an authority or incentive problem.

The manager neither withdraws the feedback nor insists their first explanation is fact. Priya neither dismisses the outcome nor accepts a vague label.

A focused diagnosis can use the final growth segment of the fixed 30-minute 1:1 over several weeks. Keep the standard 10/10/10 intact; progress one part at a time and put deeper analysis into a separate working session when needed.

Suggested sequence:

1. Engineer brings a self-assessment with two evidence examples.
2. Manager brings one reliable strength and one limiting-gap hypothesis.
3. Both compare aspiration with current organizational needs.
4. They identify missing evidence and ask relevant peers, without running a popularity poll.
5. They choose one experiment and write what each side must provide.

Good diagnosis makes development specific, fairer, and connected to real work. It remains a hypothesis that new evidence can revise.

• Start with observed behavior, effects, and corroboration—not adjectives.
• Distinguish skill, experience, and opportunity gaps.
• Choose the limiting gap for a real outcome instead of completing every ladder row.
• Explore contribution, energy, and tradeoffs beneath title aspiration.
• Managers own access and conditions; engineers own learning and action.
• Disagreement should produce a better test, not forced consensus.

This exercise creates the input for a 90-day growth contract. Engineer and manager draft independently, then reconcile differences with evidence.

The dimensions draw from these practitioner frameworks; the four-part diagnosis and conversation sequence are course syntheses.

• Monzo Engineering Progression Framework v4.1
• Dropbox Engineering Career Framework
• CircleCI engineering competency matrix
• GitLab Engineering Career Development