Shared understanding

The author suggests using stories and communicating a feature’s what for, who, and why to raise shared understanding among the team members who are building out the product, because just sharing documents is not sharing knowledge. This is an exciting process, as I can see the value of storytelling in the creation process, especially for raising creativity among the team members. Because if a member knows why they’re building something, they can be creative about tweaking it and make small decisions autonomously without relying on upper managers since they develop empathy towards the user by knowing their stories. I have been very active in startups and have extensively practiced empathizing with the user, but I have seen Jira tickets before mostly in internships, and I think they lack the detail and visual storytelling the author advocates for. Mainly it might be because people are busy and we are adopting a more remote work culture, which causes a lack of understanding and explaining stories to co-workers, which will for sure impact the quality of built features. Now I understand why Apple mandated their employees to be in person.