A piece of simple, concrete, implementable advice I read recently that I really like is "communicate in the language of options , not demands, imperatives, requests, or preferences." Imagine yourself having a conversation with your manager or someone in a relatively similar position about a decision or suggestion you have. How often do you say things like "we have to", "we need to", "we really should", "can we", or "…
Given the support for this answer I will likely get downvoted for this, but I disagree with this advice. I am a co-founder (and CTO) of a small company myself and hence get to talk to the folks in my company quite regularly. I disagree with the notion that passion or personal preference doesn't belong in a decision-making process. Not only does it belong there, it is even a critical part of it, assuming of course tha…
One day, he said, with a slightly frustrated tone, something along the lines of : "Andy: you're providing what appear to be good options and detail here - but someone in a "senior" position should recommend a path forward. Don't just give me 3 options that I need to then go and figure out for myself."
from that point on I've always tried to provide a hard recommendation - and rationale that includes a sort of decision tree approach. "We start with ______ [with good reasons to do so] then if X comes to pass we continue with it and if Y comes to pass we can pick a a different path with another option I have as backup."
The result seems to often be a discussion more about the upsides/downsides and decision tree relative to the business the organization is trying to support (a good thing) vs technical merits of the options which the technical team is trusted to be well versed in.