BUILDIT manager-side development system
Development is not additional work beside the project.
A practical guide for line managers who must create useful development, honest feedback, observable promotion evidence and stronger succession without waiting for spare time that never arrives.
A Practical Guide for Line Managers Operating Without Spare Time · 17-page practical manual.
Translate employee ambition, project consequence and organisational constraint into honest action.
A line manager may not control structure, budgets or final promotion decisions. They do control clarity, work access, feedback, advocacy and follow-through.
State the current evidence fairly
Separate performance in the present role from readiness for the next. Identify the material evidence held, missing and still needing repetition.
Create useful live opportunities
Convert gaps into packages, meetings, negotiations, forecasts, reviews and leadership responsibilities the employee can safely own.
Explain authority and constraint
Say what you decide, what you can recommend, who owns the final decision and when the employee will receive an update.
One promotion question creates three separate duties.
“When will I be promoted?” requires an assessment of readiness, a development plan for missing evidence and an honest explanation of vacancy, approval and timing constraints. Answering only one leaves the conversation incomplete.
Do not present influence as authority.
“I will get this done” becomes a broken promise when the decision sits elsewhere. Preserve credibility by promising only the action and communication you can control.
A development plan fails when the manager assumes everyone wants the same career, pace or sacrifice.
Ask separately about destination, pace and acceptable trade-offs. Contentment is not low value, and ambition is not the same as readiness.
Greater scope, team responsibility, title, income and influence—with a clear view of the pressure attached.
Technical expertise, difficult packages, claims, procurement or other work where specialist judgement creates value.
Reliable income, geographic certainty, continuity and protection of family or other important commitments.
Different projects, consulting, client-side work, contracting or eventual business ownership.
A role whose commute, hours, flexibility, health demands and mobility remain sustainable around life outside work.
The same title can represent three different career strategies.
One person may relocate and accept a difficult project. Another wants the title only in Brisbane. A third will wait rather than sacrifice evenings with young children. Understand the destination and the terms on which it remains worth pursuing.
Five useful minutes around live work can outperform a quarterly lecture.
Ask for the decision, reasoning, consequence and next step. Give one material observation and arrange another practice opportunity.
Coach the judgement—not only the output.
Ask the employee to expose their reasoning before correcting the answer. This shows whether the issue is missing knowledge, an unsafe assumption, a stakeholder blind spot or a failure to translate analysis into decision.
Finish with another observable opportunity.
A coaching comment becomes development when the employee can use it again. Name the next meeting, forecast, assessment or negotiation where the changed behaviour will be reviewed.
Advice cannot close a capability gap that requires work the person has never been allowed to own.
Map the next-role evidence and identify the live packages, meetings, reviews, negotiations and reporting responsibilities that can create it safely.
Define the decision or responsibility the next role requires—not a broad label such as “more commercial”.
Identify a real package, final account, forecast, client meeting, negotiation or team responsibility.
Transfer a clear outcome, adequate access, settlement parameters and the support needed to carry consequence.
Record the output, decision, consequence and credible witness who can independently describe the work.
Make the promised exposure visible before project pressure silently removes it.
Opportunity allocation is one of the manager’s strongest development levers.
If the employee needs client exposure, a final account, team leadership or forecast ownership, the plan must show where the opportunity will come from, who releases it and how the resulting evidence will be reviewed.
A genuine stretch assignment has purpose, authority, duration, support and review.
Exploitation merely adds next-level work indefinitely because the employee is capable and available. The short-term project benefit can create long-term disengagement.
Explain which next-role capability the assignment is intended to test and why it matters.
Give the access and decision boundary needed to own a meaningful consequence.
Set a defined period or outcome rather than allowing higher-level work to become permanent by default.
Retain management accountability and remove or defer lower-value work when load materially increases.
State what success changes for readiness, title, remuneration or the next assignment.
Use the manager test.
If the assignment succeeds, what changes for the employee? If the honest answer is “nothing”, the assignment is workload—not a pathway.
Do not disguise an unfilled vacancy as development.
The employee must own meaningful consequence while the manager controls the risk.
Choose the allocation mode deliberately. Early exposure needs more structure; near-readiness needs room to decide. Review reasoning and consequence—not only whether the task was completed.
Direct ownership
The manager or embedded senior takes the work because speed, sensitivity or immediate consequence dominates.
Guided ownership
The employee owns the work with active direction, agreed authority and checkpoints through the process.
Assured ownership
The employee completes the work independently and receives focused challenge before release.
Restore ownership
Resolve the blockage, define the standard and return the work rather than rescuing the output permanently.
Close urgent risk without destroying the development opportunity.
Delegation is neither dropping a vague problem onto a junior nor dictating every step so tightly that no judgement is required. Transfer a clear outcome, sufficient authority and a review rhythm while retaining accountability.
Improve future judgement rather than repeatedly rescuing the same output.
Set the brief, classify comments, explain the material reasoning and require the employee to close the loop. Feedback must be specific enough to use in the next live cycle.
What did the employee do or omit? Use enough examples to establish a pattern—not an indictment.
What did the behaviour change for the decision, team, client, forecast, programme or risk?
What would usable next-role performance look like in observable terms?
Where will the employee practise the change, and when will the manager review it?
Replace vague adjectives with a decision model.
“Be more commercial” and “show more maturity” force the employee to decode the manager’s private meaning. Name the missing decision, commercial effect and requested authority.
One material comment can become reusable capability.
A detailed claim assessment with no recommendation can be returned for a five-line brief: entitlement, value, evidence gap, counterargument and recommendation. The employee learns a decision model they can apply again.
Development becomes promotable when outcome, scale, judgement and credible witnesses are recorded.
Exposure is not ownership, and one successful event is not yet a pattern. Identify the evidence level rather than merely noting that the topic appeared on a CV.
Move the promotion case from opinion to repeated consequence.
“I think they are ready” is weaker than three independent situations in which the employee carried next-level responsibility and credible stakeholders relied on the result.
Clarity preserves trust even when the answer is difficult.
State current performance, readiness, opportunity and what remains outside your control. Promise only the work access, advocacy, feedback or review date you can genuinely deliver.
Promise the outcome carefully
Commit directly only where the authority genuinely sits with you and the project can still deliver the decision.
Promise the advocacy
State whether you support the case, when you will submit it and how you will communicate the result.
Promise the follow-through
Explain the approver, vacancy and budget constraints. Do not promise another person’s decision.
“Not yet” needs three things to remain credible.
Promise the action—not an outcome you cannot control.
“I will submit the case by Friday” is a promise a manager can keep. “You will be promoted next month” may not be. Good intentions do not prevent a failed promise from feeling like deception.
Help credible work become known beyond the immediate reporting line.
An employee whose career depends on one manager is vulnerable to project changes, politics and turnover. Let useful visibility follow contribution rather than theatre.
Invite the employee to present the decision or outcome they genuinely own.
Create exposure to reviewers who can assess the next-level commercial standard.
Allow fair, credible work to be experienced outside the internal reporting line.
Build more than one person who can accurately describe the employee’s judgement and contribution.
Do not hoard talent because strong people make the current project easier.
Protecting the local result by limiting exposure weakens the employee and the organisation’s broader succession system. Identify two credible people outside the reporting line who should experience the employee’s next-level work within six months.
A strong team allows critical work and context to survive movement, leave and promotion.
Use the succession map as an allocation tool—not a secret ranking of human worth. Separate fact from speculation and identify single points of failure before transition begins.
Maintain a portfolio view of the team.
Complete one sentence for each person.
“They create most value through…, they want…, the next evidence required is…, and the main retention risk is…” The answer makes work allocation, development and project transition easier to manage together.
Development needs a cadence small enough to survive delivery pressure.
Career discussions should not begin at the annual review. Use short regular conversations, deeper quarterly evidence reviews and annual direction—with commitments closed between them.
Live work and immediate feedback
Review one decision, friction point or coaching observation. Produce one clear action or practice opportunity.
Readiness and opportunity evidence
Review next-role evidence, work access, employee priorities, manager commitments and any movement in opportunity or retention risk.
Career direction and total role value
Confirm destination, priorities, mobility, acceptable sacrifice and the mix of growth, mastery, security and life integration sought.
Before formal review: calibrate and remove surprises.
After the review, record actions, owners and dates. Between review points, both manager and employee return their attention to delivery rather than leaving career negotiation permanently open.
Separate career discussion from package firefighting.
If every one-on-one is consumed by work status, the employee will eventually raise their future in a moment of frustration. Protect enough space to discuss direction and evidence deliberately.
Twelve connected chapters from manager-side translation to a sustainable development rhythm.
This is an external BUILDIT development resource. It is not company policy, an industrial instrument, a competency matrix, legal advice or a guarantee of promotion, remuneration or retention.
