Captain's log

Overview

Captain’s log, week twenty-three. We hold course for the Q3 release. Heavy seas near the payment integration; crew morale steady despite the loss of two days to the staging outage. This preset closes each week with a formal entry in the ship’s log.

What this is for

This preset solves the continuity problem. Weeks blur together, and six months in, nobody can reconstruct the journey: when the hard part was, what almost sank the project, when morale turned. Ships solved this centuries ago with the log: a short, honest entry at regular intervals, written for whoever reads it later.

The Captain’s log preset writes the entry every Friday: heading held, distance traveled, weather endured, the condition of the crew as reported in their check-ins, and any course corrections made along the way. Each entry is a satisfying close to the week on its own, but the archive is the real prize. Scroll back through three months of log entries and you have the story of the voyage, told as it happened.

Who should use this

Long-project leads who’ll someday need to tell the story of how it went. You’ll have the primary sources written week by week instead of reconstructing from memory.

Managers who do end-of-week reflection and want a format with gravity. The log entry takes the week seriously without taking itself too seriously.

Teams approaching a milestone who’ll want to look back when they land. The entry from the worst week of the voyage will be the one everyone rereads at the launch party.

The prompt

Write a captain's log entry summarizing the [ team name ] team's week. Record the heading (current goals), distance traveled (progress made), weather encountered (blockers and challenges), the condition and morale of the crew (from check-ins), and any course corrections made. Close with the heading for the week ahead.

How to use

Click here to create a new Echo using this preset. You'll be able to customize the prompt and schedule before it starts generating answers.