Operation 1
Make it a daily working practice
Use the workspace daily, extend it to the team and automate recurring work
Turn the workspace you prepared into a daily practice.
This operations lesson is for people who have completed the AI workspace setup guide. The environment produces results when you use it regularly. Establish a daily routine, then extend it to the team.
On the Addness Goals page, choose "Start today's ToDos with AI" from the "…" on the Today's ToDos heading and open it in your usual AI, such as Claude Code or Codex. AI reads the current state in Addness, works on the most important constraint and returns the result to the Goal.
Addness
Claude CodeIn the morning, choose "Start today's ToDos with AI" from the "…" on the Today's ToDos heading in Addness and open it in Claude Code. AI reads Today's ToDos and overdue Goals, prepares the overdue sales report, completes the Goal and updates its current state.
01Start Today's ToDos with AI in the morning.
Focus daily work on two kinds of Goals
On the Addness Goals page, work through Goals without due dates and overdue Goals.
The Goals page lists the Goals assigned to you. Pay attention to two categories.
| Category | Meaning |
|---|---|
| Overdue Goals | Unfinished Goals due today or earlier, displayed in red |
| Goals without due dates | Work you have decided to do without deciding when |
Both appear among leaf Goals, the smallest Goals with no child Goals. Give them appropriate due dates and complete the work. Progress on those smallest Goals advances the Goals above them.
Run the achievement loop when a leaf Goal needs more than one action
Sometimes opening a Goal reveals that one action will not finish it. Follow Chapter 2: compare the current and desired states, identify the main constraint, define and execute a ToDo, and update the current state from the result. Repeat as needed. Section 2 below explains the routine.
AI can work through it with you. Choose "Brainstorm" from "Ask AI" on that Goal's row to decide the child Goals together with AI.
1. Keep AI open and use three Addness pages
Keep Claude Code open. Use Goals, Chat and Notifications in Addness. Ask AI to handle pending chats; it reads unanswered messages and the Goal's direction, replies and marks notifications as read.
01Keep AI open while you work.
Daily work in Addness uses three pages.
| Addness page | What to do |
|---|---|
| Goals | Complete Today's ToDos, address overdue Goals and create the next ToDos |
| Chat | Respond to requests and discussions in Goal chats and read group updates |
| Notifications | Check mentions and Goal updates, then mark them as read from the top |
Keep AI, such as Claude Code, open while you work. Execute work with AI and record the results in Addness Goals. The three Addness pages show the objectives and current states. You can also ask AI to handle chats and mark notifications as read. A request to handle pending chats lets AI read unanswered messages and respond according to the Goal's direction.
Managers should also use the Members page. Check who is making progress and who is stalled, then decide where to follow up. People without direct reports do not need that additional routine.
2. Run the basic loop
- Find the main constraint for the Goal. Open the Goals page and ask what is most preventing progress right now.
- Enter a ToDo that addresses it. Press Enter on a Goal Tree row to add the next Goal, much like starting a new line. Begin the title with a clear action verb.
- Set a due date for work you decide to do. The date can be today, tomorrow or next week; choose one appropriate to the ToDo.
- Complete the work. Items due today or earlier appear in red among overdue Goals. Work through those items first.
- Break down work you cannot execute. The scope is often too large. Create child Goals until you can identify something to do in the first five minutes, then begin again.
To work with AI, press "Work on it" from "Ask AI" on a row in Today's ToDos.
If the main constraint is unclear, ask AI to identify it. You retain the final decision about what to do, as discussed in Chapter 3.
Choose ToDos from the obstacle to progress. A list of easy or available actions will not advance the Goal while its main constraint remains unresolved.
3. Create work gradually and choose today's work daily
- Create only what is needed next. The situation changes, and updated evidence can change the next correct action. Add work when you identify the constraint it addresses.
- Choose the day's work each day. Add selected Goals to Today's ToDos at the top of the Goals page. Use the “+” at the start of a row to add one, and the “−” in Today's ToDos to remove it. Add newly identified work during the day when needed.
4. Keep communication and meetings connected to Goals
Use two places for communication:
- Project-wide updates go in a group. Create a group for each project, as you would use a LINE group or Slack channel.
- Requests and discussions about one job go in that Goal's chat. The conversation remains with the Goal, so later readers and AI can understand the history. AI can handle responses and ask you about decisions that need your judgment.
Meetings with automatic minutes save the record to the Goal. For meetings or decisions made elsewhere, record the decision in the Goal before considering the work finished. Without that record, the team cannot see that progress occurred.
5. Automate recurring work and recurring decisions
Daily work reveals ToDos that repeat in the same form: weekly reports, document sorting and standard initial responses. Ask AI to handle each recurring pattern when you notice it.
Automate the sales report we prepare every Monday.
The scope extends beyond Addness. AI can do work performed on a computer, including spreadsheet updates, email drafts and document generation. For work without a fixed procedure, use autonomous decisions. See Chapter 5 and the examples in Supplementary lesson 3.
Every recurring activity you delegate reduces the work you must perform in later weeks.
6. Ask AI when something is unclear
Use AI frequently. Practical use reveals what it can do.
- An unfamiliar term: “What does context mean?”
- An unfamiliar control: share a screenshot and ask, “How do I add a due date on the Goals page?”
- An unclear next action: “What is the main constraint for the Acme proposal Goal right now?”
Claude Code and Addness are enough for the working routine. Connect the sources you already use: spreadsheets, project folders, email and calendars. Existing company information becomes AI's context.
7. Keep the number of active Goals manageable
More than 30 Goals per person is a lot; more than 50 is too many. Complete and archive Goals to keep the active workload manageable.
- Use archiving and deletion where appropriate. Deciding against unnecessary work can help the Goal. Archiving removes a Goal from the active list while retaining it for later restoration. See the Goal detail guide.
- For daily or weekly work, use a template Routine to add it automatically. See the Templates guide.
- Review the Goal Tree with AI once a week. Complete achieved Goals and revise Goals that no longer fit. That is the Goal update loop from Chapter 2. Deciding that a Goal remains appropriate is also a valid review result.
Extend the approach across the company
- Use it yourself for one week first. Run daily work from your own Goal Tree before inviting others. Your example affects whether the team adopts it.
- Assign project owners and invite those people first. Assign responsibility in the company's Goal Tree and send Addness invitations. Registering from the invitation email places each person in the company organization from the start. Begin with those owners, rather than inviting everyone at once.
- Help each owner set up their AI app. Share the setup guide. Once they sign up from the invitation email, they press "Ask AI" on the first row of "Set up Addness" on the Goals page, and AI guides them.
- Use one rule for the first week. Execute work in the usual tools, then return the result to the assigned Goal.
- After one week, check one outcome. Did you ask “How is that project going?” less often? If so, the shared record is helping. If not, find where results are missing and correct that part of the process.
The company's overall Goal Tree should be defined by someone authorized to decide its direction: the CEO, executives or department heads. The change concerns how work is organized across the company.
Avoid common adoption mistakes
The same patterns often make adoption difficult.
| Mistake | Why it causes problems |
|---|---|
| Invite everyone at once | Setup questions arrive faster than you can answer them. Begin with project owners |
| Design a perfect Goal Tree first | The right structure changes with reality. Build it gradually |
| Automate customer communication immediately | Start with work that stays inside the company; external actions come later |
| Require others to use it while staying elsewhere yourself | People maintain the work record leadership actually uses |
A daily routine for CEOs and managers
Running your own work and overseeing the company require different views. Add the Members page to your routine.
| When | Where to look in Addness | What to decide |
|---|---|---|
| Morning | Your Goals page | Select today's work and answer decisions raised in AI's morning report |
| Next | Members page | Identify who is progressing and who is stalled; follow up or inspect their Goals |
| As needed | Notifications | Check mentions and updates to assigned Goals |
| Weekly | The company's Goal Tree | Read project states and reasons for stalled progress directly from the Goals |
If you still have to ask for a project's status, find the missing result in its Goal. Before blaming a person, check whether the destination Goal actually matches the work being done.
When progress cannot be understood without asking, improve the shared work record.
Fewer meetings are one of the clearest results. Progress checks can use the Goal Tree. Meetings remain for decisions.
How the routine applies the core course
| Daily action | Underlying principle |
|---|---|
| Address undated and overdue Goals | Chapter 2: repeated actions reduce the difference between current and desired states |
| Create ToDos from the main constraint | Chapter 2: ask which issue is most critical to the Goal |
| Record results and decisions in Goals | Chapter 2: work continues after a ToDo; Chapter 6: returned results inform the rest of the team |
| Review weekly and configure Routines | Chapter 2: the Goal update loop |
| Delegate recurring work to automation | Chapter 5: automate fixed procedures and use autonomous decisions for changing situations |
Common difficulties
| Difficulty | Response |
|---|---|
| A few days have passed without using Addness | Resume with the red overdue items. There is no mandatory morning or evening schedule |
| Too many Goals make it hard to choose | Reduce the active set. More than 30 per person is a lot; more than 50 is too many. Keep the ToDos needed to address the main constraints |
| Meetings and chats produced decisions, but progress is invisible | Find decisions missing from their Goals and record them |
| Team members do not return results to Goals | Check whether the destination Goal's name and scope match the actual work |
| An invited person is outside the organization | Registering from the invitation email joins the organization. Someone who registered first at addness.com can join afterward |
| AI cannot connect to Addness | Follow the Addness MCP guide |
Review
- Undated and overdue Goals steadily decrease toward zero.
- ToDos address the main constraint and have appropriate due dates.
- Requests stay in Goal chats, and decisions are recorded in Goals.
- Project owners adopt the routine first, and status questions become less frequent.
- Recurring work moves into automation or autonomous execution as you identify it.
- The active Goal count stays within a workload you can manage.
Those practices make the Goal Loop part of daily work.
Learn more
- Using Addness: the Help Center covers individual screens, Goal sharing, templates, Routines, meetings and minutes.
- Using Claude Code: Supplementary lesson 1: A complete guide to Claude Code provides video demonstrations from installation through scheduled execution.
Learn to achieve results with people and AI.