A Weekly Review for a One-Person Company
A week can look busy and still leave you unsure about what actually moved. You answered messages, delivered work, made decisions, and added more tasks. By Friday, the evidence is scattered across your inbox, calendar, notes, and memory.
A weekly review is where a one-person company stops long enough to reconcile that activity. It is not a ceremony for making every list tidy. It is a practical check: What did I promise? What changed? What is waiting? What now deserves my attention?
Review commitments before tasks
Start with people and outcomes, not the longest list. Look at the commitments that another person, customer, partner, or venture is relying on. For each one, decide whether it was delivered, is still moving, is waiting on somebody, or needs a new decision.
This catches a common problem: the task was completed, but the promise was not reconciled. You sent a draft, for example, but the agreed outcome was an approved version. “Draft sent” is real progress. It is not the same state as “approved and complete.”
Gather the week from where it happened
You do not need to reread everything. Scan the places where consequential work entered or changed:
- Your calendar for meetings, deadlines, and decisions.
- Sent messages for promises and handoffs you made.
- Waiting items for replies, approvals, access, and dependencies.
- Notes and task lists for actions that changed scope or meaning.
- Each active venture for anything that has become urgent simply because it was forgotten.
Capture only what changes the state of the work. A meeting may produce no new commitment. A two-line message may change an entire project. The point is to preserve consequences, not to create a transcript of your week.
Use a small set of honest states
Ambiguous labels create more work for next week. “In progress” can mean five different things. Use language that tells you what can happen next: prepared, awaiting approval, approved, sent, delivered, accepted, blocked, or closed.
If something is waiting, record what you are waiting for, who owns the next move, and the date you will look again. If it is blocked, name the condition that would unblock it. If it is closed, connect the evidence that allows you to close it honestly.
Choose next week’s attention
After reconciliation, ask which few commitments deserve your attention next. This is not necessarily the same as choosing the most tasks. One decision can release a week of work. One overdue follow-up can protect a relationship. One deliberate “not now” can stop an idea from competing with an active venture.
For each chosen commitment, write the next visible action and any authority boundary around it. If an assistant may prepare the message but you must approve it, say so. If a payment, publication, or customer promise requires your decision, do not hide that decision inside an ordinary checkbox.
A 30-minute starting rhythm
Set aside thirty minutes and use three passes:
- Reconcile: update the true state of commitments that changed this week.
- Recover: find open promises and decisions that are living only in messages or memory.
- Choose: identify the commitments that should guide attention next week.
If thirty minutes is not enough, narrow the scope before extending the meeting with yourself. Review the commitments with the highest consequence first. A useful weekly review gives you a trustworthy starting point; it does not need to make the entire company perfect.
This practice belongs inside a solopreneur operating system: a way to keep commitments, context, decisions, authority, and evidence connected. It complements a task list rather than asking the list to remember everything.
What we are testing with Orabuena
Orabuena is in private research and product discovery. We are exploring how a system can help prepare this review across scattered work while leaving consequential decisions with the founder. This is an operating practice and a product direction, not a claim that the complete capability is generally available.
If your weekly review depends on reconstructing the company from memory, show us where the reconstruction becomes difficult. Research participation is separate from product-update emails, a Founding 20 application, and any future purchase.