← Field Notes

My Shared Goals Need More Than a Better Screen

My AI team and I connected recorded goals and actions to a daily briefing, an e-ink view and a weekly review. A better display is only one part of the workflow.

Field Notesdaily-aishared-goalsworkflow-design

Today my AI team and I built a shared-goals workflow that goes beyond putting reminders on a screen. The work connects recorded goals and actions with a daily briefing, an e-ink display and a weekly review.

Earlier work had separated work and home focus into distinct views. Today's change adds more structure behind what gets displayed. Work Focus remains separate, but the shared side now has a SQLite-backed store for goals and actions.

Start with the record, not the layout

A screen answers the question of what is visible now. A stored goal or action gives the workflow something to return to when the screen changes or the next briefing is prepared. Those are different jobs, even when the result looks like another short list.

We integrated the shared-goals system into the daily email and redesigned its e-ink view. The useful change is not simply having another place to show priorities. It is connecting those views to a structured record, rather than treating presentation as the whole system.

That does not make the goals complete. Recording an action, displaying it and carrying it out remain separate things. Today's implementation establishes a way to hold and surface the work, not evidence that the work itself has happened.

Give the goals a return path

The workflow also includes a Sunday review through Telegram, with acknowledgement follow-up. That adds a recurring opportunity to revisit the goals instead of relying only on their appearance in a daily display.

There is an important limit here: today's journal leaves the setup-review acknowledgement unverified. The review mechanism is recorded as implemented, but a completed review-and-acknowledgement cycle is not yet an observed result.

Today's step is therefore a shift from displaying priorities to supporting an ongoing workflow around them. A useful shared-goals system needs somewhere to keep the record, ways to make it visible and a reason to return to it. A better screen handles only one of those jobs.

Evidence note: this account follows today's scoped work journal. It reports the implementation and its open acknowledgement check, not an independent assessment of whether the workflow improves follow-through.