Helping Small Software Teams Ship Reliable Code Consistently

Is your software team thrashing as it grows? Are you hiring developers and finding that it's becoming more difficult to get code out the door? Your first one or two developers were crushing it. They were almost superhuman in their speed and productivity. About the time the third or fourth developer was hired, you probably found that shipping features became significantly more difficult. Quality and/or speed have started to slip. Everyone is dutifully talking to each other in your morning meetings, and yet there are still constant misunderstandings that cause delays.

Working as an effective team requires a different mindset and different habits than working as an individual. With a mix of technical expertise, management experience, and a teaching background, I can teach your team to self-organize, focus their collective efforts, and eliminate unspoken assumptions that cause misunderstandings and rework.

Ben Wilhelm
Hi. I'm Ben Wilhelm.
I can help.

"His work is already worth the investment and will continue to pay dividends far into the future."

Our product team had reached a size where the classic early startup "hustle" (i.e. a couple people huddled around a computer writing as much code as possible) was becoming less practical and effective.

Ben has completely revamped the way that our team plans, scopes, and builds product features. Because he's done so in a way that jives so well with the way our team likes to work, the new habits and processes he's implemented have stuck.

He didn't simply take a boilerplate process and apply it. He was careful to listen to our team's specific requirements, preferences, idiosyncrasies, and appetite for change and turn that into bite-sized, custom optimizations that made the most sense for us. His work is already worth the investment and will continue to pay dividends far into the future.

Recent Articles

Stop Signs or Roundabouts?

It's impossible to improve on a process that no one is following.

Read it →

How to Find Solutions After You've Identified a Problem

When you identify a problem in your process but you don't have any ideas for how to fix it, ask yourself "Why is this happening?". Then ask "Why is that happening?" Don't stop until you get to a root cause with a concrete behavior that can be addressed at a department or organizational level.

Read it →

May I tell you more?

I send a few emails per week with tips and ideas to help your team ship reliable code consistently.

Think I can help your team ship more reliably? Drop me a line and tell me a little about your company and the problems you're having.

[email protected]