"The engineers on my team just want to code. They don't want to have anything to do with product. They just want specs. What do I do?"

1/n Are you asking them do to X *and* do their "day job" as defined by their managers (and frankly your roadmap) ?

If so, start there...

2/n Do they have a reason to believe that doing X will in any way improve the quality of the product and make their lives easier? Have they ever seen X "work" ?

Show don't tell.
3/n Is there average day/week a quagmire of unnecessary meetings, wading through tech debt, struggling to get *anything* to work ... and jumping through process hoops to prove their worth?

If so...no they will not have bandwidth.
4/n How do incentives work on the engineering team? Maybe they want to help, but their "grade" is determined by something altogether different.

"I'd love to, but I am on the hook to deliver [some project] this quarter to make a good impression..."

Talk to eng management.
5/n Have they had any time to practice?

Or did they get thrown into the deep end the first time they were given a shot ... expected to brainstorm on demand, be as vocal as practiced PdMs and designers, and "participate" !

Make it safe to practice. Reasonable expectations.
6/n In the past, did they experience an executive crapping on everyone's ideas, and treating them badly? You'd be amazed how often this happens. A non-team-member pulls the brakes 20m in and says "ok, so WTF are we doing here?!"
7/n Say they've tried, and quit. "No more discovery meetings! Just tell us what to build!"

This is likely because they attended, but didn't feel like they added value or were able to shape the direction.
8/n They feel overwhelmed.

This is were an experienced lead modeling how to participate can really help (cc @GergelyOrosz ). They may have no role models on how this can be healthy or go down well. Just performative kickoffs that are all slides and orders, no conversation.
9/n finally....don't expect and engineer to immediately open up about their hesitations. Like anyone, they probably don't want conflict. This is where building relationships as a co-team member and eliminating the awkward PM/team power dynamic really helps.

Have a conversation.

More from For later read

There is some valuable analysis in this report, but on the defense front this report is deeply flawed. There are other sections of value in report but, candidly, I don't think it helps us think through critical question of Taiwan defense issues in clear & well-grounded way. 1/


Normally as it might seem churlish to be so critical, but @cfr is so high-profile & the co-authors so distinguished I think it’s key to be clear. If not, people - including in Beijing - could get the wrong idea & this report could do real harm if influential on defense issues. 2/

BLUF: The defense discussion in this report does not engage at the depth needed to add to this critical debate. Accordingly conclusions in report are ill-founded - & in key parts harmful/misleading, esp that US shldnt be prepared defend Taiwan directly (alongside own efforts). 3/

The root of the problem is that report doesn't engage w the real debate on TWN defense issues or, frankly, the facts as knowable in public. Perhaps the most direct proof of this: The citations. There is nothing in the citations to @DeptofDefense China Military Power Report...4/

Nor to vast majority of leading informed sources on this like Ochmanek, the @RANDCorporation Scorecard, @CNAS, etc. This is esp salient b/c co-authors by their own admission have v little insight into contemporary military issues. & both last served in govt in Bush 43. 5/

You May Also Like

1. Project 1742 (EcoHealth/DTRA)
Risks of bat-borne zoonotic diseases in Western Asia

Duration: 24/10/2018-23 /10/2019

Funding: $71,500
@dgaytandzhieva
https://t.co/680CdD8uug


2. Bat Virus Database
Access to the database is limited only to those scientists participating in our ‘Bats and Coronaviruses’ project
Our intention is to eventually open up this database to the larger scientific community
https://t.co/mPn7b9HM48


3. EcoHealth Alliance & DTRA Asking for Trouble
One Health research project focused on characterizing bat diversity, bat coronavirus diversity and the risk of bat-borne zoonotic disease emergence in the region.
https://t.co/u6aUeWBGEN


4. Phelps, Olival, Epstein, Karesh - EcoHealth/DTRA


5, Methods and Expected Outcomes
(Unexpected Outcome = New Coronavirus Pandemic)