Team Journal
A team journal is a way to quickly give a brief overview of what’s happening on the project (for INTERNAL USE ONLY). Designers have done team diaries/journals/blogs for past projects and thought we’d try spinning one up for this project.
Outcome
It serves a couple purposes:
-
It’s good perspective to read back on things and how/why we made decisions, or identify where a problem started creeping up. Don’t worry about making an entry every day or having multiple entries per day, this is all great.
-
It’s a really great start to a case study so that sales/marketing folks don’t have to start from complete scratch and search for relevant docs.
-
For Prac updates, we might be able to just point people to this.
Method
- Set up a Google doc in a Truss folder and share with project team.
- Each person can add journal entries at any time, just adds the date and their name to their entry.
- Remember candor is vital, links to external docs are helpful, and it’s ok to be informal.
- Suggestion: set up a Slackbot on an internal project channel to remind folks the journal exists.