At AutoBizz, we believe that productivity is not about working longer hours; instead it’s about having a reliable system that allows you to focus on meaningful work without keeping everything in your head.

We follow principles inspired by Getting Things Done (GTD), developed by David Allen, with adaptations that fit our way of working.

One Core Principle:

Your brain is for thinking, not for remembering.

Instead of trying to remember everything, we capture, organize, review, and execute work through our systems.

Our goal is simple:

• Reduce stress

• Improve reliability

• Avoid forgotten tasks

• Create transparency

• Deliver high-quality work consistently

Our workflow follows five simple steps:

1. Capture

2. Clarify

3. Organize

4. Execute (Engage)

5. Review (Reflect)
   

1. Capture Everything

Whenever something requires action, don’t rely on memory. Capture it immediately. 

We work at a fast pace at AutoBizz. When something isn't captured immediately, it doesn't just disappear, it turns into a gap. Context gets lost, and that gap resurfaces later as a missed follow-up, a confused handoff, or a blocker for the next person who needed that information.

Capturing isn't extra admin work. It's what prevents today's fast pace from becoming tomorrow's fire drill for you, and often for the whole team depending on you.

Examples:

• Client requests

• Meeting action items

• Slack messages requiring follow-up

• Bugs and issues

• Ideas and improvements

• Internal requests

Rule: Never trust your memory with commitments.

Key Quote

“Always have just one place to capture, be it physical or digital"

2. Clarify Before Starting

Avoid vague tasks. Capturing a task only gets you halfway. A task like "Talk to client" is captured but not usable; whoever picks it up still has to guess what it means, and guesses are where mistakes start.

Clarifying closes that gap. It turns "something I need to remember" into "something anyone on the team could pick up and execute correctly, even without asking you first." That's what keeps fast-paced work from turning into rework.

Bad examples:

X → Check inventory

X →Talk to client

X → Update dashboard

Good examples:

•  Verify inventory discrepancies for SKU list

•  Send project update email to client

•  Update Meta Ads ROAS dashboard with last week’s data

Every task should answer:

• What exactly needs to be done?

• What is the expected outcome?

• Is there enough information to start?

Key Quote

“People don’t even understand what they captured in hurry after 24 hours"

3. Organize Work Properly

Everything should have a place. At AutoBizz, work belongs inside systems, not inside people’s heads.

Use:

• Clickup tasks

• Subtasks

• Documentation

• Due dates

• Assignees

• Priorities

Large Work ⇒ Projects

If something requires multiple steps, break it down.

Example:

Client Dashboard Automation

Subtasks:

• Gather requirements

• Audit source data

• Build workflow

• Design and develop the metrics

• QA

• Deliver to client

Every Project Needs an Active Worker

A project with five assignees and zero people actively pushing it forward isn't organized but stalled, and it looks fine from the outside.

At AutoBizz, this is handled through two fields:

• Assignees: everyone who may touch this task or project.

• Active Worker: the one person currently moving it forward right now.

For a project (the parent task), only the Project Lead/PM sits in Active Worker which is intentional, as they are the one actively leading the project. So they can see the full picture and clear blockers before they turn into delays. For a subtask, the Active Worker is whoever currently has the ball.

Rule: A subtask should never sit with assignees but no Active Worker for long; that's exactly how work quietly stalls without anyone noticing.

Handing off to the next person:

1. Update the Active Worker field to them.

2. Leave a comment with the context they need, don't make them ask you what's going on.

3. Only change the Status once the work itself is actually complete.
   

Ideas That Aren't Urgent Yet (Proposed) 

Not everything captured needs action right now. A good idea, a "nice to have" client suggestion, or something worth revisiting next quarter still deserves a place to live; otherwise it either clutters the active task list or gets forgotten entirely.

Based on AutoBizz's existing status list, "IN FUTURE" status built for exactly this work that's been captured and scoped but isn't being actively worked on yet. remember:

• Still create the task with what you know & don't leave it as a Slack message or a mental note.

• Set its status to IN FUTURE rather than Not Started (Not Started implies it's queued to start soon; IN FUTURE signals "not yet, on purpose").

• Revisit IN FUTURE items during the monthly/quarterly or especially when there is nothing to do, review so they don't get permanently forgotten.

Two-Minute Rule

If something takes less than two minutes, do it immediately instead of creating unnecessary overhead.

Examples:

• Reply to a message

• Rename a file

• Confirm meeting availability

• Send requested screenshot

Key Quote

“If it’s not in the system, it doesn’t exist. If no one owns it, it won’t move.”

4. Execute the Right Work (Engage)

Being busy is not the same as being productive. Focus on:

High Priority Work First

1. Urgent client issues

2. Scheduled deliverables

3. Team dependencies

4. Improvements

5. Nice-to-have tasks

Within Each Priority Tier

Knowing the priority order tells you what matters most. These checks help you decide what to actually start next once you're inside a tier.

• Context: batch similar work. Jumping between task types burns focus. Where you can, group similar work together; for example, handling everything that's IN COMS/RESPONSE status in one block, or batching review work, rather than bouncing between client replies, build work, and reviews all morning.

• Time available: If you only have 20 minutes before a meeting, don't start something that needs two hours of focus rather pull from Two-Minute Rule tasks, or something you can safely pause mid-way.

• Energy available: Match the work to your actual state, not your ideal one. Save deep client-facing or complex build work for when you're sharpest; use lower-energy periods for review, documentation, or quick replies.

Use the Clickup Priority field (Urgent / High / Normal / Low) alongside the status feature. Use it consistently so the whole team can trust it at a glance.

Avoid

• Constant multitasking

• Context switching

• Keeping too many tabs open

• Working from memory

Communicate Early

If blocked:

• Do not disappear.

• Inform the relevant person immediately.

• Good communication prevents delays.

Key Quote

“Work smarter. Focus better. Deliver what matters.”

5. Review Regularly (Reflect)

A system only works when maintained.

Daily Review

Beginning of the day:

• Check priorities

• Review today’s tasks

• Understand deadlines

End of the day:

• Update task status

• Capture unfinished work

• Prepare tomorrow

Weekly Review

Review:

• Completed work

• Overdue tasks

• Upcoming priorities

• Dependencies

• Blockers

Ask yourself:

• What is pending?

• What needs follow-up?

• What should be delegated?

• What should be documented?

Key Quote

“Review daily. Reflect weekly. Keep the system moving.”

Special Notes:

1. Meeting Action Items

Meetings do not create progress. Actions create progress. Never leave meetings with unclear responsibilities.

Before every meeting:

• Client meetings: the AutoBizz team member responsible for that account or deliverable prepares the agenda in advance.

• Internal meetings: the organizer, or the person the meeting was set up for, prepares the agenda in advance.

• No agenda, no meeting. If you're unsure who owns the agenda for a meeting type not listed here, ask before it starts; don't assume it'll sort itself out live.

After every meeting:

1. Confirm the outcome out loud before the meeting ends like what was decided, what happens next.

2. Capture decisions.

3. Record action items.

4. Assign owners.

5. Set deadlines.

6. Update Clickup.

Note on Meeting Notetaker: 

Fathom Notetaker helps with notes and summaries, but it doesn't replace personal ownership. Each teammate should still capture their own action items as the meeting happens; don't wait on Fathom's output to know what you're responsible for.

2. Waiting for Others

Sometimes progress depends on someone else.

Examples:

• Client approval

• Team feedback

• Access permissions

• Data availability

Track these items and follow up proactively.

How we track this:

• If the next step depends on a teammate, update that task's Active Worker to them and leave a comment explaining what you need, don't just wait silently.

• The task's Status only changes once the work is actually complete; reassigning Active Worker is what signals "the ball is now in someone else's court."

• The Project Lead/PM is responsible for reviewing the project's full view regularly (see Daily/Weekly Review) to catch anything that's been sitting without progress so don't rely on the blocked person to always speak up first.

Never assume that others will remember; instead, take a more proactive approach and remind them.

3. Common Mistakes

• X → Keeping tasks in your head

• X → Waiting until something becomes urgent

• X → Working without updating Clickup

• X → Not communicating blockers

• X → Trying to multitask everything

• X → Leaving meetings without action items

• X → Assuming you’ll remember later

4. Expectations at AutoBizz

We value:

• Reliability over busyness

• Transparency over assumptions

• Communication over silence

• Systems over memory

• Ownership over excuses

• Consistency over intensity

The AutoBizz framework also names the failure modes explicitly - the habits that undermine even well-intentioned teams:

• Keeping tasks in their head instead of in a system

• Working without updating task statuses

• Not communicating when blocked

• Leaving meetings without assigning action items

• Multitasking as a default instead of a last resort

• Assuming memory is a reliable backup plan

None of these are signs that someone doesn't care about their work. They're signs that no one has given the team a better system.

Final Thought

Productivity isn’t about doing more. It’s about making sure the right things get done, at the right time, with less stress and more clarity. A good system allows you to focus your energy on creating value instead of remembering what you might have forgotten.