are.na An Application by Charles Broskoski www.are.na Build ideas mindfully. Save content, create collections, and connect ideas with other people. ObsidianRoam ResearchWhat this site isOn Motivation thinkingnetworkshypermedianotetaking
On Motivation An Essay by Charles Broskoski www.are.na I’ve had this (semi-vague) idea that I want to write about what keeps us excited to work on Are.na, on the occasion of its 10th (yes 10th) birthday. While writing generally is a tricky process for me, this subject motivation is even trickier. In turning this subject around in my mind, and thinking about all the people and things that have been influential, I have some idea about what keeps us going. Nodal pointsInfinite varieties of contextsA lifelong projectGrowing in the correct way are.naThe slow blade penetrates the shield
Viability, usablity, feasibility In an empowered product team, the product manager is explicitly responsible for ensuring value and viability; the designer is responsible for ensuring usability; and the tech lead is responsible for ensuring feasibility. The team does this by truly collaborating in an intense, give and take, in order to discover a solution that work for all of us. However, in a feature team, you still (hopefully) have a designer to ensure usability, and you have engineers to ensure feasibility, but, and this is critical to understand: the value and business viability are the responsibility of the stakeholder or executive that requested the feature on the roadmap. Marty Cagan, Product vs. Feature Teams svpg.com What went wrong? teamwork