Sleepers A Poem by Nick Trombley m o t i o n l e s s m o t i o n l s e s m o t i o n s l e s m o t i o s n l e s m o t i s o n l e s m o t s i o n l e s m o s t i o n l e s m s o t i o n l e s s m o t i o n l e s s o m t i o n l e s s o m t i n o l e s s o m t n i o l e s s o m n t i o l e s s o m n t o i l e s s o m n o t i l e s s o m n o t l i e s s o m n o l t i e s s o m n o l i t e s Concrete poetry sleepeuphony
Because we have to sleep Two nights later, as he was getting ready to bed down, the boy looked for the star they followed every night. He thought that the horizon was a bit lower than it had been, because he seemed to see stars on the desert itself. "It's the oasis," said the camel driver. "Well, why don't we go there right now?" the boy asked. "Because we have to sleep." Paulo Coelho, The Alchemist sleep
To carve a volume into the void of darkness The nocturnal sound is a reminder of human solitude and mortality, and it makes one conscious of the entire slumbering city. Anyone who has become entranced by the sound of dripping water in the darkness of a ruin can attest to the extraordinary capacity of the ear to carve a volume into the void of darkness. The space traced by the ear in the darkness becomes a cavity sculpted directly in the interior of the mind. Juhani Pallasmaa, The Eyes of the Skin: Architecture and the Senses sounddarknesssleepsolitude
Traced in the summer skies Yes, it was the hour when, a long time ago, I was perfectly content. What awaited me back then was always a night of easy, dreamless sleep. And yet something had changed, since it was back to my cell that I went to wait for the next day…as if familiar paths traced in summer skies could lead as easily to prison as to the sleep of the innocent. Albert Camus, The Stranger sleepcrime
Product vs. Feature Teams An Article by Marty Cagan svpg.com This article is certain to upset many people. Empowered product teamsViability, usablity, feasibilityWhat went wrong? featuressoftwareagile
Empowered product teams When I wrote about the virtues of empowered product teams, I was referring to what I’ll continue to call here as product teams. Specifically, they are cross-functional (product, design and engineering); they are focused on and measured by outcomes (rather than output); and they are empowered to figure out the best way to solve the problems they’ve been asked to solve.
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. What went wrong? teamwork
What went wrong? If something ships from one of the companies I advise, and it is virtually unusable because of poor design (which as we all know occasionally does happen), you can bet I go directly to the designer and ask how this happened? It is absolutely on the designer to ensure this does not happen, so something went wrong. Similarly, if the product ships and performance is terrible you can bet I go directly to the tech lead with the same question. And most frequently of all, if something ships and the analytics show that it’s either not being bought or not being used, or it turns out that it violates some business constraint like compliance or privacy, you can bet I go right to the product manager with that question. Viability, usablity, feasibility