Problem statement
There are standard descriptions of the Open Home Foundation that you can use whenever you need to introduce us: whether in event bios, recruitment materials, press materials, partner communications, or anywhere else you need a quick (or more detailed!) explainer.
They capture our core messaging, based on what's already available on our website, newsletters, and other materials. We've created them in three different lengths so you can choose what works best for your needs.
Currently, there's a misalignment between how each of our projects is perceived and how we want to convey what they are and communicate it in a consistent and coherent way. Therefore, we want to create a database with standard descriptions for each of them, starting with Home Assistant, as part of the visual design work in progress at the moment.
Community signals
No response
Scope & Boundaries
In scope
- Boiler plates for Home Assistant
-- Long version
-- Medium version
-- Short version
-- One-liner
Not in scope
- Full brand personality/identity work
- Brand tone of voice
Foreseen solution
No response
Risks & open questions
- These boilerplates might require sign-off from project key stakeholders, which might delay decision-making and approvals
- It's also dependent on the existing Visual Design work in progress
Appetite
Small/Medium: half cycle, considering some work already in place (Home Assistant)
Execution issues
No response
Decision log
Problem statement
There are standard descriptions of the Open Home Foundation that you can use whenever you need to introduce us: whether in event bios, recruitment materials, press materials, partner communications, or anywhere else you need a quick (or more detailed!) explainer.
They capture our core messaging, based on what's already available on our website, newsletters, and other materials. We've created them in three different lengths so you can choose what works best for your needs.
Currently, there's a misalignment between how each of our projects is perceived and how we want to convey what they are and communicate it in a consistent and coherent way. Therefore, we want to create a database with standard descriptions for each of them, starting with Home Assistant, as part of the visual design work in progress at the moment.
Community signals
No response
Scope & Boundaries
In scope
-- Long version
-- Medium version
-- Short version
-- One-liner
Not in scope
Foreseen solution
No response
Risks & open questions
Appetite
Small/Medium: half cycle, considering some work already in place (Home Assistant)
Execution issues
No response
Decision log