Ask vs. Guess Cultures

Jun 15, 2017 | Newsletter

Subscribe to Engineering Impact, the weekly newsletter for managers of software teams.


 

This week: Why you should expose developers to customer pain, how to build the perfect release deck, a culture clash that often goes unrecognized, how to (effectively) ask engineers questions

 

how companies can ship high quality software faster

LEADERSHIP

Faster, Better, Cheaper

James Sinclair on how companies can ship high quality software faster—by exposing developers to customer pain.

Read the full post →

 

How to make a kick-ass software release deck

PRODUCTIVITY

The art of the release deck

John Witchel, founding CTO at Prosper, with a practical guide to building the perfect release deck—so you can communicate effectively and help the rest of the company quickly understand the updates your team has made.

Read the full post →

 

how to tell whether your engineering environment is an ask or a guess culture

CULTURE

Ask vs. Guess Cultures

Have you ever been told you’re “too direct?” Or, on the other side, do you think others are often too confrontational? Katherine Wu, an engineer at Heroku, on the differences between Ask vs Guess Cultures—a clash that isn’t often recognized, yet causes quite a bit of tension and frustration.

See the slides & the talk →

 

how to communicate with your engineers effectively

EFFECTIVE COMMUNICATION

How to Ask Questions The Smart Way

Engineers are notoriously hostile to people who seem to be unwilling to think or to do their own homework before asking questions. Eric Steven Raymond on the smart way to ask a question in order to get a rapid and responsive answer.

Read the full post →

 


 

Ben Thompson

Ben Thompson

Ben Thompson is a co-founder at GitPrime where he leads design and customer experience. He is a Y Combinator alumni, with a background in product design, branding, and UX design. Follow @thebent on Twitter.

Get Engineering Impact: the weekly newsletter for managers of software teams

Keep current with trends in engineering leadership, productivity, culture, and scaling development teams.

how to use data to lead a successful software teams

A Data Driven Approach To Leading Software Teams

Learn how engineering leaders are using data to help their team increase productivity and become even more effective. We've analyzed over 40 Million commits to help you understand the important questions every software engineering manager needs to know.

Success! Please check your email for your download. You might also be interested in Engineering Impact: the Weekly Newsletter for Managers of Software Teams. Keep current with trends in engineering leadership, productivity, culture and scaling development teams.

Share This