I got my Computer Science and Management degrees at the University of Maryland.

Having worked in startups, enterprise, education, and research, I've seen the full gamut of problems that engineering teams encounter. 

And I've coached my colleagues through hundreds of problems and blockers that got in the way of Getting Work Done.

Not just through thorny technical problems (plenty of those too), but through the politics of making things happen at the team and organizational levels.
 

Engineers are quite good at figuring out how to solve technical challenges.

But that's not what holds them back and frustrates them the most.
Even when you write a great PR, solve a thorny architecture problem, or find a tool that makes work a lot easier, you're only half-way there to achieving impact.

The first half you could do on your own.

But if you want your team on board, avoid alerts when you're not on-call, and rest easy knowing that someone else won't screw up your code later, there's ONE KEY PROBLEM that you have to solve.

 

It's INEFFECTIVE COMMUNICATION. That's inefficient influence, in-actionable insights, and silo'd success stories.

How many times have you:

• Struggled with talking to Product peers in terms that they understand?
• Been frustrated with hours of repetitive meetings to get a technical initiative onto the roadmap?
• Seen teams do duplicate work because they weren't aware of other's efforts?
• Introduced a key technology to your organization, and had ZERO adoption?
• Spent hours explaining your PR to more junior colleagues, so that you could get an approval?
• Wasted hours commenting on junior colleagues' PRs with basic code quality feedback?
• Wondered if your PR really did have no issues, or if your colleagues were just too overwhelmed to comment with feedback?