Step 1: Get clear on what you are asking for

Know the curriculum, the length, the format, the outcomes, and the exact cost before you open your mouth. Vague asks get vague answers. Pick two or three things in the program that map directly to work already on your plate this quarter. Not aspirational work. Current work. The kit gives you this language, already written, for whichever program you are enrolling in.

​

Step 2: Find out what your company already offers

Check the employee handbook, the intranet, and your onboarding docs for professional development, tuition assistance, or continuing education policy. There is usually something in there, and it is usually forgotten.

Then ask a person. HR or your manager, whoever is closer. Questions worth asking:

• Is there a per-employee development budget, and what is the amount

• Is it use-it-or-lose-it, and when does it reset

• Who approves it, and is that different above a dollar threshold

• Is it paid up front or reimbursed after completion

• Is there a tenure or repayment agreement attached

That last one matters. Find out now, not after you sign.

​

Step 3: Build the business case

Two paragraphs, not ten pages. What problem the team has, and what changes once you have gone through this.

Anchor it to something your leadership is already measured on. Ramp time. Forecast accuracy. Manager coaching consistency. Win rates in a specific segment. Attrition on a specific team. If the outcome you claim does not appear on somebody's dashboard, pick a different outcome.

Then compare the program cost against one thing it helps you avoid: a contractor engagement, an external hire, a vendor-led training, a stalled deal. You do not need a precise number. You need a comparison that makes the cost look small next to the alternative.

​

Step 4: Line up the funding

If the cost fits inside your development budget, this is a short conversation. If it does not, come with options instead of a problem:

• Split the cost. You cover a portion, the company covers the rest. This one closes more often than any other version of the ask.

• Split the timing. Half this quarter, half next, so it lands across two budget periods.

• Borrow from an adjacent budget. Team enablement, headcount savings from an open role, unspent conference or travel dollars. Somebody in your org is sitting on money they will lose at the end of the period.

• Ask for the exception. If the program clears the standard budget cap, ask for an exception rather than assuming the cap is the answer. Caps are set for volume, not for specific cases.

​

Step 5: Get ahead of the objections

You already know what is coming. Answer it before it gets asked. "When are you going to do this?" On your own time. Say the schedule out loud so it stops being a question. "How do I know it worked?" Name what you will bring back and when. A rebuilt onboarding path. A revised forecast process. A coaching cadence you run with your team. Something they can see. "What if you leave?" Some employers ask for a tenure commitment or a repayment clause. Decide how you feel about that before it comes up, and know what you are willing to sign.

​

Step 6: Put it in writing

Send a short written request even if the conversation already went well. One page: the program, the cost, the timeline, the outcomes, the funding option you are proposing. Verbal approvals evaporate when the approver changes roles.

Then book fifteen minutes to walk them through it. Do not make your manager read and decide alone.

​

Step 7: After the yes

Get the approval in writing, and get the reimbursement process in writing with it. Which form, which system, which receipts, what deadline. Keep your manager posted while you go through it. A two-line update after each module is enough, and it turns your development into something they feel good about having funded.

Then actually apply it. Share something with your team inside the first month. That is what makes the next request easy, for you and for the person who asks after you.