- handbook
- Company
- Company
- Board & Investors
- Communications
- Decision making and project management
- Guides
- Organizational Structure
- principles
- Remote Work
- Security
- Access Control Policy
- AI Development and Customer Data Policy
- Asset Management Policy
- Business Continuity & Disaster Recovery Policy
- Cryptography Policy
- Data Management Policy
- Hardware Security Policy
- Human Resources Security Policy
- Incident Response Plan
- Information Security Policy and Acceptable Use Policy
- Information Security Roles and Responsibilities
- Operations Security Policy
- Risk Management Policy
- Secure Development Policy
- Third-Party Risk Management Policy
- strategy
- values
- Operations
- Engineering & Design Practices
- Design
- Engineering
- Contributing
- Front End
- Packaging Guidelines
- Platform Ops
- Deployment
- FlowFuse Dedicated
- Incident Response
- Observability
- Production Environment
- Self Hosted Assistant
- Staging Environment
- Update Stacks on Production
- Product
- Blueprints
- Feature Catalog
- Feedback
- Glossary
- Market Segments
- Metrics
- Node-RED Dashboard
- Personas
- Pricing Principles
- Principles
- Product Growth
- Product Swimlanes
- Strategy
- Versioning
- vision
- Project Management
- Releases
- Security Policy
- Support
- tools
- Internal Operations
- People Ops
- Coaching Plans
- Code of Conduct
- Compensation
- Compliance & Regulatory
- Expenses
- Hiring
- Holiday & Leave
- Job Descriptions
- Account Executive
- CEO
- Chief of Staff
- CTO
- Developer Relations Advocate
- Engineering Manager
- Fullstack Engineer
- Fullstack Engineer (AI-Focused)
- Head of Marketing
- Product Manager
- Product Marketer
- Solutions Engineer
- Technical Product Manager
- VP of Sales
- PeopleOps Policies
- Performance review
- Summit
- Marketing department
- Marketing
- blog
- Brand Voice
- Community
- Company Messaging
- Customer Stories
- Events
- FlowFuse for Education
- How we work
- Lead Activation
- Lead Generation
- Marketing Programs
- Social Media
- Webinars
- Website
- Sales department
- Sales
Tasks are the primary way to track work that needs to happen on behalf of the CEO. The goal is to keep all tasks self-contained: every task should hold enough context that anyone picking it up can act on it without needing to dig through email threads or ask for background.
High-priority items must always be surfaced, even when the CEO is operating at a higher strategic level and less involved in day-to-day execution.
Task anatomy
A well-formed task includes:
- A clear, action-oriented title
- The relevant context — links to emails, documents, or calendar events
- A due date or target timeline
- An owner (the CEO, a delegate, or the executive assistant)
- Any dependencies or blockers
When new context arrives (e.g. a reply in a related email thread), update the task immediately. The task is the source of truth — not the inbox.
Daily workflow
Each workday, review all open tasks. Run through the following checks:
- Match inbox items to tasks. Cross-reference the inbox with open tasks. If an email relates to an existing task, add the context to that task and note any updates.
- Check scheduled tasks. For each task with a due date or scheduled start: is the timeline still realistic? Does anything need to be moved earlier or later?
- Assess readiness. Is the task ready to be executed today — or is it blocked? If blocked, note what is needed and by whom.
- Identify delegation opportunities. Which tasks can be handled without the CEO? Reassign where appropriate and update the owner on the task.
- Flag tasks that need time blocked. If a task requires focused CEO time (e.g. writing, reviewing, a decision), create a calendar event for it and link the task in the event description.
- Surface urgent or high-priority items. Any task that is overdue, at risk, or requires an imminent CEO decision should be flagged in the daily touch-base.
Scheduling and timelines
A task on the list without a realistic timeline creates noise. When reviewing tasks:
- If a task has no due date, assign one or flag it for prioritization.
- If a due date has passed without completion, either reschedule it with a new date and a note explaining the delay, or escalate to the CEO.
- Avoid piling too many tasks on a single day — spread work to match the CEO's available focus time.
Delegating tasks
Not every task requires the CEO. Before keeping a task assigned to the CEO, ask: can this be handled fully or partially by someone else?
When delegating:
- Update the task owner.
- Include enough context in the task that the delegate can act without a handoff call.
- Set a follow-up date to check on completion.
Blocking time on the calendar
Some tasks require uninterrupted focus time. When a task needs a dedicated block on the CEO's calendar:
- Create a calendar event following the event anatomy guidelines.
- Link the task directly in the event description so context is one click away.
- Keep the block appropriately sized — avoid over- or under-allocating time.
- If the task is completed before the block, release the time.