Topic

Workflow design

Where does the work get stuck?

A process diagram may leave out the spreadsheet, mailbox, or repeated approval that takes up most of the week. Following recent cases helps you find those gaps.

Follow recent cases, separate active handling from elapsed time, and preserve disagreements between the brief, practice, and policy. Any proposed change still needs someone who owns the process and can decide what is allowed.

Notes in this topic

  1. 4 min read

    What changes for the customer?

    A customer can have a ready account and still be unable to do the job they bought the software for. Follow that job before choosing an AI feature.

    Read the note
  2. 5 min read

    Which parts should become shared capability?

    Repeated work may justify shared code. First separate the reusable job from each team's data, policy, and responsibilities.

    Read the note
  3. 7 min read

    Build, buy, adapt, or leave it alone?

    Your current software may do enough already. Check the difficult case before deciding what to buy or build.

    Read the note
  4. 6 min read

    The work takes minutes. Why does it take a week?

    A faster draft won't help much if the case still waits three days for a missing record. Find where the time goes before choosing what to automate.

    Read the note
  5. 6 min read

    Who needs to be in the room?

    An engineer can build the draft, but who can check the figures, approve its use, and support it next month? Reserve those people's time before promising a pilot.

    Read the note
  6. 5 min read

    Find your first workflow by following recent cases

    Start with recent work and the people who handle it. A small investigation can reveal a useful question without pretending to measure the whole company.

    Read the note
  7. 6 min read

    The brief is wrong. What do you do next?

    Keep the original promise, show where it conflicts with the work, and ask what the team should build instead.

    Read the note
  8. 6 min read

    Which parts of this workflow need a model?

    A model can read a vague request while code checks the rules. Split those jobs before choosing a technology.

    Read the note
  9. 6 min read

    Is this workflow worth automating?

    A painful process can still be a poor investment. Follow the work, check the numbers, and find out what would have to be true for a change to pay off.

    Read the note