Growing Beyond Your Current Responsibilities

Name the capability you want to build

Growth is not the same as becoming busier. Start by naming a capability that would expand the work you can reliably do: presenting findings, training a colleague, planning a small project, or understanding a neighboring function. Connect it to a direction you care about and a need the organization recognizes. A vague wish for more responsibility is hard to act on. A request to coordinate one small handover improvement, with feedback from an experienced colleague, is easier to discuss. Check whether the capability requires formal training or supervised practice before you volunteer to perform it independently.

Design a manageable stretch

A useful assignment is difficult enough to require learning but limited enough to complete responsibly. Specify the output, the people affected, the decision boundaries, and the duration. For example, organizing a single internal workshop is different from owning the entire training program. Ask what existing work should be reduced or delayed. Taking on everything can damage current performance and turn development into exhaustion. Identify a sponsor or reviewer who can answer questions and assess the result. If support is unavailable, shrink the assignment or begin with observation. Ambition does not remove the need for capacity, authority, and guidance.

Make the proposal easy to evaluate

Explain the organizational benefit alongside your learning goal. A concise proposal might say: I would like to improve our new-starter checklist over four weeks, using two agreed hours per week, with the team lead reviewing the draft. State what you will not own and how you will gather feedback. Ask how successful completion will be recognized, while avoiding assumptions that one project automatically guarantees a promotion. If the opportunity is declined, ask what condition would make it feasible or which smaller experience could prepare you. A refusal can reveal a timing or resource problem rather than a judgment that you cannot grow.

Convert experience into learning

At the end, compare the intended output with what happened. Ask for feedback on both the result and your way of working. Record a concrete example of a skill you improved, a mistake you corrected, and the next practice you need. Share useful documentation so that the organization benefits after the assignment ends. Keep a private, nonconfidential record of your contribution for future development conversations. Watch for a pattern of permanently expanding duties without corresponding authority, support, or discussion of recognition. Growth should increase your capability and options, not merely normalize an unlimited workload. Revisit the agreement when the scope changes.

Observe someone who already performs the capability well and ask what choices are hardest. The visible output may hide preparation, judgment, and coordination. This observation can help you choose a better stretch assignment and avoid mistaking a senior person’s authority for a technique you can simply copy without the same responsibility or context.