URL: https://www.scottsmitelli.com/articles/no-but-engineer/
Improv isn’t just a collection of screaming jackasses; there are actually a number of rules that each performer should abide by to make the scene work well. Most of these rules boil down to two things: 1) always add new information, and 2) always accept and respect the information added by others in the scene.
The rules of improv work quite well when you’re making up a comedy scene. They permit each participant the freedom to propose something potentially ludicrous, but with the guaranteed assurance that their contribution will not be rejected. It’s a remarkably safe and supportive environment, and actually one of the least frightening forms of acting that an anxious or shy person can dip their toes into. The yes-and framework lays the groundwork for completely absurd and potentially hilarious situations to blossom. This is exactly what you want in a comedy scene.
This is precisely the opposite of what you want on your engineering team.
People go into tech for a variety of reasons. Some see the allure of easy money, others feel as though it may be one of the lazier paths through life. But for a number of us, the motivation is a desire to be useful. Something inside compels us to always look for problems to solve, processes to improve, or simply things to do. The word “useful” is a very deliberate choice; it does not automatically imply that the work is helpful.
If the intention of “yes, and” is to kite a given situation to newer and increasingly absurd heights, then “no, but” implies the exact opposite: a default position of rejecting the proposal while simultaneously offering an acceptable substitute. In a room full of yes-ands, a single well deployed no-but can bring the conversation back down to reality.
An effective no-but engineer possesses a healthy mix of experience and insight, paired with a probably-unhealthy mix of skepticism and distrust. Those are hard things to identify sometimes, and they don’t really lend themselves to any sort of curriculum for self-study.
The no-but engineer:
- Is not a dickhead.
- Is tactful.
- Is well aware of the broader organization, its needs, strengths, and bottlenecks.
- Knows what's going on under the hood.
- Has seen some things.
- Is pragmatic
- Does not seek glory, and accepts responsibility for failures.
- Hears what others mean, not just what they say.
- Is absolutely not a "rockstar" in terms of productivity.
- Embodies the spirit of "The Gambler" from that Kenny Roger's song.