…and to add a few thoughts around automations:
Automations in the end are the underlying technical representation of a real-world “homeflow” (I don’t like workflow there as a word 
), or pain point, or need.
Example: “I don’t want to waste energy when I air out the bathroom in winter”
Automation representation of that: “if the zigbee magnet window contact opens, switch off the zigbee radiator walve”.
Improving the organisation and creation of automations in their current form does help the John-Persona to get things done quicker for the Jane- and the Margarete-Persona, but for Jane and Margarete themselves nothing changes => little to no impact on the HAF northstar.
To just quickly scribble an idea which I didnt validate at all, but still:
How about we give HA the concept of self-definable “household entities”. These entities have a represenation in the real world, but can be made up of multiple underlying “tech entities”. Example: the household entity “fridge” might under the hood contain a wifi power meter plug, a zigbee door contact and a zigbee thermo sensor. Jane and Margarete don’t have to (and don’t want to) care about zigbee and wifi and magnet contacts, andandand. But having a “fridge” entity lowers the threshold to create your own “Hey homeassistant, remind me to close the fridge when it’s open for more than a minute” homeflow. On the side it would tie in nicely with the whole assists voice control landscape…
We already have the concept in rooms, but in my opinion more granular entities could help.
Anyway, enough braindump for today, let me know if you’d like to continue the conversation, inside or outside this thread. I’d love to