I read Storytelling with data and right after that I read it again while listening to the audiobook narrated by the author.

This book was written for data analysts.
It's important to understand the following two roles in Business Intelligence:
Data Analyst and BI Developer/ Analytics Engineer.

I'll use a headcount report as an example. To create a report in that topic, I had to learn to communicate with the HR system's API to extract the data. It involved reading the system documentation multiple times, testing the API with Postman and learning PowerShell to call the API and insert the data to an SQL Server. To create the report I had to create a data model and make sure to implement and double-check the business logic to end up with the correct numbers with the requested dimensions to slice the data.

This process and these kind of activities require a particular technical minded skill set, I had to write code in PowerShell, T-SQL, M and DAX. My argument is that being good at the technical part of creating a report does not make one a subject matter expert.

A data analyst is a person who can take data from different sources, create a report, draw conclusions and present the related data via a reporting tool and or presentation tool. This person could answer questions about the reasons behind changes in headcount over a time period across dimensions such as departments, positions and so on. Ideally, a data analyst is using data sources created by their colleagues in the BI team.

Report design and formatting

A data analyst creates a report for a particular purpose, to tell a story by focusing on and highlighting the relevant data points. Enterprise reports do not have a story because that story is dependent on the viewer and the time period or the many dimensions you can slice and dice the data with.
Report consumers can have very different (Row-Level Security) security settings on the same report, some can see all data, some only their business unit.
Unlike reports created by a single analyst, enterprise reports are created by collaboration heavily influenced by the stakeholders. While a BI developer is not in control of report design and formatting choices, it would be a big mistake to neglect improving their skills in this area. Reading and or listening to Storytelling with data gives you tools to make better design choices in order to help the report consumers use the report and bring clarity to what they see.
The real value of the book is that it makes you more conscious of your design choices.