Skip to content
Operatingculture-and-messaging

Culture, messaging and availability

What we stand for, how we say it, and who is reachable this week.

A culture record pairs a behaviour with a concrete example of it from someone's own week, and optionally with the anti-pattern. A messaging record pins one audience: the persona, the voice, and what we will not claim. Availability puts the week's meetings and the notes people want you to keep in mind on one page.

  • 8 company principles kept in the repository
  • 1 audience per messaging record
  • 20 messaging records a draft may read

How it works

From an empty record to something you can act on, in the order you do it.

  1. 1

    Write the behaviour, then the example

    The title is the behaviour, the context is why it matters, and the example is one thing that actually happened.

  2. 2

    Add the anti-pattern and an owner

    Plus a review date. Active is refused without them, and the missing field is named rather than guessed.

  3. 3

    Pin the messaging to one audience

    Persona, voice and preferred language, then what we will not claim to that audience.

  4. 4

    Keep availability current

    Set yourself busy with a duration or until you clear it, and add notes with a category and a date range.

In the app

What it looks like

Captures of Growth-OS itself, rendered with sample data rather than our own records.

Culture records above the principles kept in the repository.
Culture records above the principles kept in the repository.
A culture record with its required example and its anti-pattern.
A culture record with its required example and its anti-pattern.
A messaging record with its voice and the words we avoid.
A messaging record with its voice and the words we avoid.

The problem this solves

What goes wrong when this work lives in spreadsheets, documents and one person's memory.

A value nobody can act on

Be customer obsessed tells you nothing on a Tuesday. A recorded example from someone's own week does.

A draft that overclaims

Without a stated boundary every reviewer argues from taste. The avoid field gives them something to point at.

A blank calendar row read as free

The view states plainly that missing data does not mean somebody is available, and the in-meeting indicator describes the schedule rather than live attendance.

Highlights

Why it matters

A principle needs an example

What good looks like is required. Without it a value statement is a poster, and nobody can act on a poster.

The words we will not use are a field

A reviewer can point at it. That is what makes a draft reviewable rather than a matter of taste.

Company principles and project records stay apart

The centrally kept principles are read only and sit above this project's own records. A project record may quote one, never replace it.

Honest limits

What this does and does not promise

  • Company-wide principles change through a reviewed repository change, not from this screen.

  • A draft generator reads at most twenty messaging records and you cannot choose which twenty. The text travels as data, never as instruction, and the record ids it used are recorded with the copy.

Questions

Frequently asked questions

Do this work in Culture, messaging and availability

The page opens on this project's records. The in-app guide describes every field.