Twice a month, I bring together a small group of software professionals and leaders online to explore the situations they're actually dealing with right now.
Join the next free session
Maybe it's a technical decision you haven't made yet. Working together with a colleague being tough. A customer who expects something different from what your team is building. Or something you know you should deal with, but keep postponing.
You're the senior developer or team lead, and you keep doing a ton of work that others could do. What are you holding onto that somebody else could do? Why aren't you delegating it? And what needs to change?
So you don't ask. You assume they are busy, and therefore wait, work around it or make the decision yourself. But are you sure that person is too busy to help? Or did you just assume that yourself?
The last 6 times, they delivered too late. So should you just accept their word the 7th time? What stops you from questioning their planning?
You thought the request was obvious. The developer thought so too. A week later, the dev shows you a solution that isn't what you expected. Where did it go wrong?
You thought this was an early functional version. Your customer expected something that already looked polished. What did you assume without realizing it?
Sometimes it's about architecture or requirements, sometimes about communication or assumptions. And sometimes we go deeper: what is happening inside you that makes you respond the way you do? That helps you recognize the same pattern the next time.
There are no slides and no fixed list of items to go through. Everyone gets time for their situation. I ask questions and challenge assumptions. When it's not your turn, put yourself in the other person's position: what would you do? Sometimes it's easiest to recognize your own pattern in somebody else.
Looking for something to put on in the background while answering email? Then this isn't for you.
Joost Vunderink. More than 25 years in software development, as a developer, architect, team lead, advisor and CTO. Building better software is also about asking better questions and having conversations you'd rather avoid. That's the territory I like to explore.
Come with a problem, and leave with the next step clear in your mind. Choose a session and leave your details. I will contact you to confirm your spot.
I may contact you personally before or after the session about your participation. I won't add your number to an automated calling list. After registering, you'll receive the practical details and a few short questions to help you choose the situation you'd like to discuss.
Hope to hear from you soon!