Product blog

Product blog

Product updates, field guides, and field notes—each with links to docs and the hub where relevant. High-level milestones also appear on the changelog.

  1. Abstract gradient suggesting dual displays and calm focus

    Field notes · Mar 29, 2026

    A calmer two-screen desk: separating encode from ops without losing focus

    Why a second display matters for focus, how to reduce notification noise, and how to keep “mission control” from stealing cycles from the work audiences actually see.

    • Ergonomics and attention
    • Roles and handoffs
    • Closing the loop
    • Designing the desk for long sessions

    Field notes

    Read
  2. Abstract gradient suggesting community and moderation balance

    Field notes · Mar 29, 2026

    Online communities that scale without burning out moderators

    Policy, tooling philosophy, and human-in-the-loop habits that keep servers lively without turning moderators into clocks.

    • Least privilege and training
    • Long-term memory
    • Escalation and mental health
    • Building community norms proactively

    Field notes

    Read
  3. Abstract gradient suggesting email and owned channels

    Field notes · Mar 29, 2026

    Owned email versus algorithmic feeds: building consent and cadence

    Why inboxes reward consent, how social feeds reward velocity, and how to repurpose without duplicating canonical URLs.

    • What belongs where
    • Operational habits
    • List hygiene and deliverability
    • Measuring what email actually contributes

    Field notes

    Read
  4. Abstract gradient suggesting retail and software boundaries

    Field notes · Mar 29, 2026

    Commerce and software: why mixed carts confuse customers and finance teams

    A plain-language look at carts, subscriptions, support queues, and compliance when physical goods and SaaS live under one brand.

    • Support routing
    • Partners and creators
    • Finance and forecasting
    • Customer education as a billing risk reducer

    Field notes

    Read
  5. Abstract gradient suggesting data and uncertainty

    Field notes · Mar 29, 2026

    Reading stats and predictions: methodology beats vibes

    How to ask what a metric means, what window it covers, and what it cannot say about the future.

    • Practical checks
    • Communicating uncertainty
    • Sampling and survivorship
    • Building a healthier relationship with forecasts

    Field notes

    Read
  6. Abstract gradient suggesting automation and safety

    Field notes · Mar 29, 2026

    AI-assisted workflows in small teams: guardrails before glamour

    Scopes, approvals, audit trails, and kill switches—before you chain tools that can touch real systems.

    • Kill switches
    • What to automate first
    • Documentation
    • Vendor evaluation

    Field notes

    Read
  7. Abstract gradient suggesting documentation and structure

    Field notes · Mar 29, 2026

    Multi-product companies need clear URLs and stable documentation

    Information architecture for teams that ship more than one product—without turning every page into a maze.

    • Internal habits
    • Search and discovery
    • Onboarding and support
    • Keeping documentation systems honest over time

    Field notes

    Read
  8. Abstract gradient suggesting editorial workflow

    Field notes · Mar 29, 2026

    Content operations for small teams: calendars, links, and one home base

    A lightweight workflow for planning, publishing, and reusing content without a full enterprise CMS.

    • Review and risk
    • Metrics that matter
    • Collaboration and tools
    • Distribution and discovery after publishing

    Field notes

    Read
  9. Abstract gradient suggesting rhythm and pacing

    Field notes · Mar 29, 2026

    Sustainable publishing cadence: batching without burning out

    How to set a rhythm you can keep, protect quality, and recover when life interrupts the schedule.

    • Quality bar
    • Recovery
    • Energy and creativity
    • What sustainable really looks like at 12 months

    Field notes

    Read
  10. Launch readiness illustration

    Field notes · Mar 29, 2026

    Launch checklists that prevent rework and protect trust

    Checklist rigor reduces rollback probability and support spikes.

    • Split launch into readiness, execution, and follow-through
    • Use explicit go/no-go criteria with owners
    • Plan rollback and communication in advance
    • Run post-launch review within 72 hours

    Field notes

    Read