A README is essentially a manual for software projects. This is a manual for understanding my quirks and how I think we might work effectively together. I am more than open to change and welcome any feedback or suggestions!
- First Principles Thinking helps reduce bias and assumptions.
- Design for empowerment. Replace bottlenecks with self-service when possible and allow your users/customers to accomplish their goals with the least amount of friction.
- Lead as a gardener, less as a chess player.
As the PM, it is my job to:
- Empower the team by helping them understand the WHO & WHY we’re betting on an initiative
- Say no to good opportunities so that we can say yes to great ones.
- Working Hours: M-F 10:00-18:00 EST
- Preferred Meeting Times: M-Th 11:00-15:00 EST
- Location/Timezone: Long Island City, NY (EST)
I’d recommend the following Eisenhower Matrix for contacting me:
| Urgent | Not Urgent | |
|---|---|---|
| Important | (e.g. Clients locked out of accounts) Zoom or Phone Call | (e.g. Request feedback on the latest spec) Slack DM tagged “Not Urgent” |
| Not Important | (e.g. Respond to a complaint email) Don’t let me be a bottleneck 🙃 | (e.g. Dank meme to share) Slack DM/Tweet |
I tend to favor asynchronous communications but understand it’s not always feasible.
- Face-to-face meetings are expensive and should have at least an objective for what we hope to reach by the end.
- My favorite type of meeting is what I call “jam sessions”. Allocated time for divergent exploration in a problem space. Think of this as visually collaborative brainstorming.
- Seeing is believing. I strongly believe seeing a mockup, diagram, or napkin doodle communicates far more effectively than without.
Things that give me energy vs take it away
| Boosters ⬆️ | Drainers ⬇️ |
|---|---|
| API Design | Migrating Enterprise Systems |
| Developer Experience Design | |
| Zero to One Products |