Founder of FiftyThree, Georg Petschnigg, in one of the Bēhance interview mentioned the process of creating additional colors for the Paper app:
“When we released additional colors, our deadline was dependent on nature, so as we were writing code, we were noticing the temperature change and were racing to finish before the leaves changed color. It was thrilling to have this reminder all around you, and it also humanizes the entire process, rather than just working towards milestone 1.3. This episodic approach means that the product experience is incomplete if the narrative isn’t being fulfilled.”
Such a rational idea turns processes into a natural flow. It brings emotions to team members. It brings life to the product. It brings fun to the team.
Github promotes “unprocess” and self-managing, but there must be processes within a organization to enable scale. The process eliminates efforts for dev teams empirically when it solves the right problem. Unfortunately, if process is assigned without questioning its rightfulness, it will create waste. I guess the take away is that we should keep reviewing the product whether it can naturally fulfill our need to achieve the objectives.