2 ms·
Too many things wrong here. Quick thoughts. Hope they help (non-exhaustive): * This is generic human communications failure, not an engineer/non-engineer comms
by renewiltord 6y ago
Too many things wrong here. Quick thoughts. Hope they help (non-exhaustive):
* This is generic human communications failure, not an engineer/non-engineer comms failure, i.e. you have incompatible communication styles. They like meetings, you like async reports. Do what is necessary to align this in future. Action item: "Hey, guys, I think I'm better able to express this in a report. I'll send you one every day/week/month". Alternative: "Hey, guys, I need continuous blocks of time to work. Can we schedule our sync at the beginning of my day".
* Explicit communication is superior to all else. Requesting ACKs is superior to all else. Action item: Set calendar event to 24 h after weekly report (send on Thursday or Monday), 2 h after daily report, subject: "Ask team if they read report, post abstract in team chat channel"
* Rapid feedback is key in early companies. The rest of your team may believe that the product does not deserve firming up (say the TAM is lower than projected, you're not getting traction, etc.). Assuming "maintainable and certified" may be misunderstanding objectives. Action item: Prioritize understanding where people stand. Default prioritize order: Make it work, make it right, make it good.
In any case, team failure is usually team failure not individual failure. Presumably your friends will provide validation of your self-worth so I have provided no indictment of the rest of your team. Still, it is expected of those with executive authority (your CEO) to communicate these things to you.