Here there is no mastery of unnameable creative processes, only the patience of a craftsman, chipping away slowly; the mastery of what is made does not lie in the depths of some impenetrable ego; it lies, instead, in the simple mastery of the steps in the process, and in the definition of these steps.
One question that is still hard to answer after 10 years of working on Are.na is “what is the long term vision?” This is difficult for a few reasons.
One reason is that we have to calibrate our definition of long term with the person who is asking the question. Are.na is a lifelong project. Our ideal outcome as a company is not becoming the next Facebook (god forbid), it’s becoming the next Nishiyama Onsen Keiunkan, a hot spring hotel in Japan, and one of the world’s oldest businesses (founded in 705 AD).
The Lean Portfolio Management function that controls funding, are given sole authority to approve which Portfolio Epics move into each stream. Epics are not explanations about a problem that needs to be solved. They are pre-formed ideas about how best to solve those problems.
Right away we can see signs of the old-school mindset of viewing teams as a “delivery” function instead of a strategic one. The high level thinkers come up with ideas, and the low level doers execute on those ideas. Ignored is the possibility that those closest to the work might be best equipped to make decisions about it. Escaping from this misguided mindset is a core goal of Agile thinking that SAFe fails to remotely accomplish.
In all this focus on volume metrics, estimation, and churning work through the pipeline, the concept of what’s actually valuable or successful is easily lost. It’s often assumed that more work shipped out the door must be “value”, even if the experience of the product is actually suffering and users are not benefiting from the additional features.