JaredMake the work easier to move forward.
A founder's morning can start in five different places: a customer thread, a project update, an unanswered proposal, a meeting agenda, and yesterday's decisions. Give Jared the relevant context and a clear time horizon. The useful output is a short briefing that explains what needs attention, why it matters, and who can move it forward.
The loudest conversation is not always the most important. A routine update can bury a decision that blocks the team, while an old concern keeps resurfacing after it has been resolved. A good briefing separates facts from questions and ties each priority to a current source. It should help you choose your next move without pretending to choose your business strategy.
What to bring to the task
- The channels and connected records relevant to this week's company priorities.
- Your current goals, decision owners, and the period the briefing should cover.
- Upcoming meetings, agreed deadlines, and customer commitments worth checking.
- Known exclusions, such as confidential topics that do not belong in a shared team briefing.
From context to a useful result.
Set the decision window
Start with today, the next review, or another explicit period. Identify the audience and the decisions reserved for the founder. This keeps a daily briefing from becoming a history of everything happening in the company.
Gather the relevant context
Use the conversations and connected records your team makes available. Look for the latest stated status, an owner, and the next promised step. Treat conflicting updates and missing information as questions to resolve.
Prepare the priorities
Group the briefing into decisions, commitments, and watch items. For each entry, include the reason it matters now and a proposed next step. Make the supporting context easy for the reviewer to find.
Review and direct the work
Read the briefing in Slack, correct the priorities, and decide what should happen next. Any proposed message or change to a connected tool remains a separate action for human approval.
The human review checkpoint
You decide priorities, make commitments, and approve external writes. A prepared briefing does not authorize Jared to send a customer message, change a deadline, or update a business record. Financial figures should be checked against the responsible source before you act on them.
Before you make it a routine
- Is each priority relevant to the chosen time window?
- Does every urgent item explain the consequence of waiting?
- Are decisions clearly separated from informational updates?
- Are uncertain dates and statuses visibly unresolved?
A few useful questions
Does Jared decide what I should do?
Jared can prepare a proposed order from the context you provide. You make the call, especially where priorities involve strategy, money, people, or a commitment to someone else.
What if a source is missing?
The briefing should say what is missing and why it matters. Start with available context and ask the relevant owner to confirm the gap before relying on that item.
Can the briefing be shared with the whole team?
Review the audience and remove restricted information first. Preparing it in your workflow does not make every underlying conversation appropriate to share. Any external write requires approval.