Workflows Directory

Find your team’s next superpower.

Results

7 workflow templates

  • App data requirements

    When the requirements for an internal app leave fields or actions unclear, the business systems analyst gets one data specification: entities, fields, who reads and writes each, and every unresolved name as a question. Nothing is built or changed.

    Starts it
    Business systems analyst
    Brings
    export, notes, document
    Gets
    9 outputs
  • Business continuity plan

    For an owner or operations manager: the activities the business cannot stop for long, how long each can be down and how much data it can lose, what each depends on, the fallback for each, and named owners, deputies, contacts and a test date, ready for a competent reviewer and the owner's approval.

    Starts it
    Owner
    Brings
    export, notes
    Gets
    7 outputs
  • Cloud spend variance bridge

    When cloud or tooling costs move away from budget, the finance lead and the engineering manager get a bridge from budget to actual by service and cost owner, with usage beside each large move, the unallocated and shared costs, and the questions each side must answer.

    Starts it
    Finance lead
    Brings
    export, notes
    Gets
    6 outputs
  • CRM field ownership map

    Before a CRM sync or field mapping changes, the systems owner gets a field map from the supplied exports and sample records: each field's source, match keys and conflict rule, with unclear keys, consent fields and duplicates left as questions for each field's owner.

    Starts it
    Systems owner
    Brings
    export, notes
    Gets
    7 outputs
  • Notification channel plan

    When a business event needs to notify people, the integration owner gets one channel plan from the event definitions: trigger, urgency, who is told by which channel, what needs confirmation, fallbacks and reply handling. Consent and message rules stay as questions. Nothing is sent.

    Starts it
    Integration owner
    Brings
    export, notes
    Gets
    1 output
  • Service inbox routing plan

    When a new service inbox is being set up, the service owner gets a routing plan: each approved address, the queue it should reach and who owns it, checks to run before it goes live, and the wrong-address risks, loop risks and unconfirmed queue owners still open. Nothing is configured.

    Starts it
    Service owner
    Brings
    export, notes
    Gets
    5 outputs
  • Workflow inventory

    When the ownership and status of your automated workflows come up for review, the platform owner gets one inventory built from the exports supplied: environments, enabled states, last run, queued runs and owner gaps. Quiet workflows become questions, not removal lists.

    Starts it
    Platform owner
    Brings
    export, notes
    Gets
    7 outputs