Not to toot my own horn, but that second example is almost verbatim how I talk with engineer, and pretty much anybody who knows how to specify a problem and dev

Not to toot my own horn, but that second example is almost verbatim how I talk with engineer, and pretty much anybody who knows how to specify a problem and devise hypotheses for solutions. I’ve been told that this is approach is completely different and depending on who you are either refreshed unnerved shocked excited etc… Generally, the people that have the hardest time with this kind of direct approach, have the least capacity or ability to actually build or change or implement something. Think along the lines of chief of strategy, often times it’s a COO, most likely though it’s somebody within the sales BD realm who is non-technical, or somebody in the operational side who is not technical but was put into a technical leadership role. Alternatively, people who really love this have been waiting to be empowered to do what they know is correct but have generally been impeded by other people who have opaque goals. These are mid-level software engineers, junior software engineers, often times though it’s most impactful to senior engineers who are super cynical or burnt out and just playing out the clock.