How do you invest in your own development?

This week's Assembly asked
"How do you invest in your own development?"

We've gathered the key points and notes from the session, so you can refer back for future reference, or if you weren't able to join, learn from your fellow freelancers.

Nobody's doing it as well as they think they should be

The most common feeling in the room was that professional development is important, clearly valued, and fairly easily deprioritised. When work is busy, there's no time. When it's quiet, the energy isn't there. Nobody is nudging you, booking you onto things, or setting aside budget on your behalf. You have to do all of that yourself, and its easy for something else to get in the way. Plus it's entirely self-directed - there's no-one else making you do it.

Informal and formal learning both count — but they work differently

Reading, watching, listening, picking things up from peers and projects: all valuable, maybe not even treated as development. But there's a real difference between absorbing something passively and actively learning it and applying it. Formal training, accredited courses, certifications, structured programmes, they tend to be perceived and stick differently. Maybe because there's investment attached, maybe because it produces something you can point to.

A plan makes a real difference

It's essential to have a target: a direction you want to move in, an idea of what you need to learn to get there, and some committment or investment into it. Else, you're just booking an hour a week without an idea of what you'll be doing with it.

Track what you're learning, not just what you're doing

There's real value in keeping a development log — not just of courses and certifications, but of the things you've picked up and applied. The steep learning curve of setting up as a freelancer counts. Learning how IR35 works counts. Getting on top of a new AI platform counts. It doesn't need to be client-facing to be valuable. A running record of your own development gives you something to look back on, and something to draw from when you're making the case for yourself to a new client.

Clients want to see application, not just acquisition

Certifications and qualifications carry weight in some contexts. But what tends to land better with clients is the pairing of the learning with the doing: not just "I completed this course" but "I used that approach in this project, and here's what it produced." The portfolio grows over time, but it's worth thinking early about how to connect the development you're doing with the evidence of it in practice.

Timing matters — protect the right slot in your week

Blocking time for development is smart, but think about when. Friday afternoon might be the worst possible time. Mid-week, when your brain is still properly online, tends to be more productive. The specifics will vary, but the principle holds: if you're going to treat development as real work, schedule it like real work, in a slot where you'd actually do real work.

The risk of not doing it is gradual, then sudden

Falling behind doesn't feel like anything in the short term. You keep delivering, clients keep hiring you, nothing breaks. But brilliance has a half life. Skills that were valuable three years ago carry less weight now, and the pace of change isn't slowing. The freelancers who stay relevant tend to be the ones who treat development as ongoing rather than occasional — curious by default, and open to changing how they work as well as what they know.

Words of the week: POETS and PIVOTS.

Thanks for coming along! Enjoy the long weekend.