Ask any experienced manager where they learned to lead and they will almost always describe a job, not a course: the first time they ran something they were not quite ready for, in front of people who would see the result. Yet when a small business needs more capable people, the usual response is to book training. Courses have their place. They teach concepts, vocabulary and methods, and give people a safe place to practise. But without real work to apply them to, most of what is learned fades within weeks.
The opposite mistake is just as common. Businesses assume that because everyone is busy and under pressure, everyone is developing. They are not. Work that is demanding but tightly specified, where the person has no room to choose an approach, teaches compliance, not judgement. A business can run flat out for years and grow almost nobody.
This article explains what makes an assignment genuinely developmental, how to choose work the business can safely hand to someone who is still learning, what support turns challenge into learning, and how to make sure the capability stays in the business rather than in one person’s head. It is general information for owners and managers who want to build the next layer of capability in their team.
What makes an assignment developmental
Three conditions need to hold together:
- New responsibility: the person carries something they have not carried before, such as a whole job, a customer relationship, a budget or a team.
- Real latitude: they can choose how to approach it, be wrong, and correct it. Pressure is not the active ingredient; latitude is.
- Visible consequence: the result matters and others will see it, beyond their immediate supervisor.
Two out of three is not enough. A difficult job with no latitude builds endurance. A free hand on work nobody cares about builds little. Responsibility, latitude and consequence together are what force people to develop judgement.
Challenge is not the same as opportunity
Not all hard work builds the same capability. Cleaning up a problem, such as an unhappy customer, a failing supplier or a job already off track, builds resilience and composure. Creating something, such as a new service, a new customer or a new process, builds the ability to set direction, take calculated risks and influence people without authority. Both are valuable, but they are different.
Look at who gets which kind of work. A business that hands difficult clean-up jobs to everyone but gives the chance to build something new to only one or two favoured people will look fair and will not be. Nobody designs that pattern; it emerges from habit, and only a deliberate look at recent assignments reveals it.
Shadowing is not an assignment
A common development arrangement is to make someone a deputy or have them shadow an experienced person. It usually transfers information but withholds consequence, which is the part that develops people. If the deputy never makes a decision that stands when the senior person would have chosen differently, they are observing, not leading.
Deputy arrangements can be made developmental by handing over real decision rights within a defined boundary: “You decide the crew and sequence on this job; I will only step in for safety issues or anything over $2,000.” The boundary protects the business. The decision rights create the learning.
Two rules that choose different people
Every time work is allocated, two rules compete. One says: give it to the person who will learn most. The other says: give it to the person most likely to deliver. In most cases they point to different people, and the second rule wins quietly, because its consequences arrive this month. The result is that development stops exactly when the business is busiest.
The answer is not to pretend the tension away. It is to decide in advance, for specific pieces of work, which rule applies, and to accept that on developmental assignments the business is trading a slightly lower expected result for capability it cannot get any other way. Write that decision down. A trade nobody records gets reversed under pressure.
Choose work the business can safely carry
Not every job can be used for development. Sort upcoming work into two groups:
- Protectable: a less experienced person could hold it, mistakes would be noticed in time, and failure would be recoverable and contained. These are development opportunities.
- Critical: the most capable available person must do it, because the consequence of error is serious or irreversible, such as safety-critical work, the business’s largest customer at a sensitive moment, or an urgent recovery with no time for coaching.
Good development work often includes investigations that support a later decision, small prototypes or trials, process improvements with a clear owner, well-defined parts of a larger job, and pilots of new services. Each should still have a real customer and clear acceptance criteria. Development does not remove accountability for a useful result.
Small businesses often find the list of protectable work is shorter than expected. That is useful to know. If the business needs two new supervisors within a year and its work offers only one suitable assignment, no training budget will close the gap. The options are to create assignments, for example by splitting a large job so part of it can be led by someone new, to hire, or to change how work is organised so fewer supervisors are needed.
Support turns challenge into learning
Challenge without support is not development; it is sink or swim. Support should not take ownership away from the person. It provides a scaffold:
- A briefing on purpose, constraints, customers and risks.
- Agreed decision boundaries and points where the person must check in.
- Regular short reviews, focused on decisions and reasoning, not just progress.
- Access to experienced people, who explain why they would do something, not only what.
- Feedback from the work’s customer at the end.
- A review of what happened, what assumptions held and what the person would do differently.
As the person shows competence, widen the decision space. Supervision that never relaxes teaches dependence.
Ask experienced staff to make their reasoning visible. “I would check access hours before ordering materials, because I have been caught out twice” teaches more than a checklist item with no explanation. The forgetting curve article explains why practice and spaced reinforcement matter more than one-off instruction.
Make the learning transferable
Two things make experience more valuable. First, help the person move from “what happened on this job?” to “what principle did I learn?”. The lesson may not be that a particular customer was difficult; it may be that agreeing who decides changes early prevents arguments later. That kind of lesson travels to new situations.
Second, capture what the business learned, not just what the person learned: an improved checklist, a better quote template, a note on a supplier’s lead times, a short demonstration for others. The aim is reuse, not paperwork. Otherwise the capability walks out the door with the person, and the business remains dependent on a few individuals. The key person dependence article covers that risk.
Develop working relationships, not just individuals
A business can have capable individuals and still coordinate poorly. Much of what makes a team effective sits between people: trust, shared understanding of how things work, and knowing who to ask. Development that focuses only on individual skill misses this. Assignments that cross boundaries help build it, such as a workshop hand spending a week with the estimator, an office manager running a small improvement with the production team, or two people from different parts of the business solving a customer problem together. These build relationships that make later coordination faster. Check, too, that what the business rewards matches what it asks for. Asking people to collaborate while praising only individual output teaches the opposite lesson.
Watch for capability debt
When short-term delivery always takes priority over training, handovers and process improvement, a business builds up a kind of capability debt. Jobs get done through overtime, outside specialists or the same two experienced people, but the business’s underlying ability does not grow. It looks productive while becoming more fragile. The signs are familiar: the same problems recurring, the same people indispensable, and each new job relearning things from scratch. Setting aside a small, regular share of work for development is how the debt gets repaid. The how much change a business can carry article covers fitting that into real capacity.
A worked example
This is an illustration. A 15-person electrical contracting business relies on the owner and one senior electrician to run every job. The owner wants a leading hand to be able to run small and medium jobs independently within a year.
The owner lists the work expected over the next six months and sorts it:
- A switchboard upgrade at a hospital: critical, safety-sensitive and run by the senior electrician.
- A tender for a council maintenance contract: important and time-pressured; the owner leads it, with the leading hand helping on pricing.
- A warehouse lighting retrofit for a long-standing customer: protectable.
- A pilot of a new solar system maintenance service: protectable and new.
- Several small office fit-outs: protectable, but routine.
The owner decides the warehouse retrofit is the first developmental assignment and records the trade: it may run a little less smoothly than if the senior electrician ran it, and that is accepted. The leading hand will run it end to end: reviewing the quote, scheduling, ordering, managing the crew and dealing with the customer.
The boundaries are agreed in writing. The leading hand decides crew, sequence and materials. Variations over $2,000, anything affecting safety, and any change to the price go to the owner. They meet for 20 minutes each Friday to review decisions, not just progress. The senior electrician is available for technical questions.
The job finishes a week late but within budget, and the customer is satisfied. In the review, the leading hand identifies the main cause of delay: access to the warehouse floor was limited to two nights a week, which nobody confirmed before scheduling. The business adds “confirm access hours and restrictions” to its job-start checklist, so every future job benefits.
The next assignment is the solar maintenance pilot, chosen because it builds a different capability: shaping something new with no existing method. The leading hand also becomes the person who shows a newer apprentice how to run the small fit-outs, which reinforces their own learning and starts the next layer.
How this applies to a small Australian business
- List upcoming work and sort it into protectable and critical.
- Choose developmental assignments deliberately, and record the trade.
- Make sure each has new responsibility, latitude and visible consequence.
- Give deputies real decision rights within clear boundaries.
- Provide a support scaffold: briefing, boundaries, reviews and feedback.
- Widen decision space as competence grows.
- Capture lessons in checklists, templates and demonstrations.
- Look at who gets which kind of work, and spread opportunity fairly.
Signals worth watching
- The same one or two people get every important job.
- Training is attended but never applied.
- Deputies who never make a decision that sticks.
- Clean-up work given widely, new opportunities given narrowly.
- Lessons from jobs that live only in people’s memories.
- Development plans that stop whenever the business gets busy.
Common mistakes
- Assuming busy people are developing.
- Handing over hard work without latitude.
- Using critical work for development, or never using any.
- Withdrawing support too early, or never withdrawing it.
- Measuring development by course attendance.
- Letting the learning stay with one person.
Frequently asked questions
Is training a waste of money? No. It works best when people have a real assignment to apply it to soon afterwards, and a manager who reinforces it.
What if the developmental assignment goes badly? That is the risk the business accepted by choosing protectable work. Review it honestly, focus on decisions rather than blame, and decide whether the person needs more support or a different next step.
How much latitude should we give? Enough that the person makes real decisions about approach. Set boundaries for safety, money and customer commitments, and widen them as confidence grows.
Should we pay more for developmental assignments? That depends on your pay structure. Recognition matters more than payment in most cases: make the contribution visible.
We are too small to have spare work for development. Then build it into normal work: split jobs so parts can be led by someone newer, and have experienced staff explain their reasoning as they go.
Questions to ask
- Which upcoming work could someone still learning safely hold?
- Who has had the chance to build something, rather than fix something?
- What decision rights do our deputies actually have?
- What support will each developmental assignment need?
- How will we capture what the business learned, not just the person?
- Where are we running up capability debt?
Bringing it together
People learn to lead and to handle complex work mainly by doing it. Make assignments developmental by combining new responsibility, real latitude and visible consequence, and choose work the business can safely carry while someone learns. Decide in advance which assignments are for development and record the trade, because the urge to give everything to the safest pair of hands is strongest when the business is busiest. Support the person without taking over, widen their decisions as they grow, and capture what the business learned so the capability stays when people move on.
Source: KEVOS notes, drawing on teaching material on experiential learning, developmental assignments, action learning, project-based capability development and capability management, and D. Day’s review of leadership development. Examples and figures in this article are illustrations. This article is general information.
