Building the workflow, before the software.

Why defining the work first leads to better tools, cleaner automation, and systems people actually use.

• Painted across the top of the band: the category rail, with BUILDING AT QUILL current.
• Painted above the headline: the trail BUILDING AT QUILL / RICK’S FIELD NOTES.
• Painted beneath the headline: the byline RICK LOFTON, FOUNDER, COO, CTO, MARKETING DIRECTOR, and the line 12 MIN READ, UPDATED SEPTEMBER 2026.
• Painted to the right: a six-step diagram reading OBSERVE, MAP, SIMPLIFY, ASSIGN, BUILD, IMPROVE.

• Save articleSaving needs an account, and accounts are not open yet.
• ShareNo share service is connected, so this is artwork. The address bar holds the page address.
• Listen when availableNo audio file exists in the delivery, which is what the painted label itself says.
• PrintThis is painted artwork rather than a control. Your browser can print the page.

• The read time and the update month are painted into the master. They are carried as part of the artwork and are not generated, tracked or kept current.

Start with the work, not the tool

The article opens: most software problems begin before anyone writes code. A team buys a tool, adds automations, and expects the work to become clearer. But software cannot repair a process no one has defined.

• Pulled out in the plate: “Software should support a clear way of working. It cannot create clarity on its own.”
• 1. Start with the work, not the tool: begin with people, not software. Observe how the work actually happens.
• 2. Make the invisible workflow visible: document the current state, and map the steps, delays and duplication.
• 3. Simplify before automating: remove unnecessary steps, duplicate approvals and handoffs that add no value.
• 4. Define ownership before automation: name the person responsible for every decision, record, exception and outcome.
• 5. Choose technology that supports the process: evaluate fit, integration, data ownership, security, accessibility, maintainability, cost, and an exit plan.
• 6. Build in layers and verify: foundation, core workflow, integrations, automation, reporting, optimization, each with human review.
• Painted in the sidebar: ON THIS PAGE, listing the nine parts of the article, and RELATED STORIES.

• On this page, all nine entriesThe band is one supplied image, so the painted control cannot change what it shows.
• Related story: Choosing the Right AI Tools That Actually Move the Needle
• Related story: Automation Without Clarity Accelerates ConfusionNo page exists for this headline, so it is shown as artwork rather than a link.
• Related story: Ownership Is the Operating SystemNo page exists for this headline, so it is shown as artwork rather than a link.
• View all stories
• The Weekly Brief: enter your email, and Get the briefNo newsletter service is connected. Nothing is collected, stored or sent, so this is artwork rather than a signup.
• View all articles

• One line of the painted body text is garbled in the master itself, in the third paragraph of part 2. The clean text around it is carried above; the garbled fragment is not reconstructed or guessed.
• The sidebar paints a short ABOUT RICK LOFTON card reading that Rick writes about practical systems, workflow design, software, and building Quill Productions. Nothing further about any person is added here.

The workflow-first framework, in practice

Part seven closes the article: track what matters, and use what you learn to make small, consistent improvements.

• Measured on the band: cycle time, error rate, rework, completion rate, customer experience, adoption.
• 01 OBSERVE: watch the work in its natural state.
• 02 MAP: document steps, decisions, data, and handoffs.
• 03 SIMPLIFY: remove waste and clarify inputs.
• 04 ASSIGN: define an owner for every step and outcome.
• 05 BUILD: add technology that supports the work.
• 06 IMPROVE: measure results, refine, and repeat.
• WHAT THIS LOOKS LIKE IN PRACTICE, painted as three cards: THE REQUEST, a growing business asks for a custom portal and automation to streamline client work; THE DISCOVERY, mapping reveals duplicated entry, unclear approvals, and scattered files across teams; THE SOLUTION, Quill designs one intake, clear ownership, shared data, and phased automation.
• PRACTICAL CHECKLIST, eight painted items from “define one business outcome” through “pilot, measure, and revise before scaling”.
• FIELD QUESTIONS, eight painted questions from “what starts the work?” through “how will we know it improved?”
• Closing line, painted in a rule: “What will this system make possible that the team cannot do reliably today?”

• The eight checklist boxesThe checklist is painted into the image and nothing records a tick, so the boxes are artwork rather than controls.
• Map your workflow with Quill
• HelpfulNo feedback service exists, so nothing would be recorded.
• Needs more contextNo feedback service exists, so nothing would be recorded.
• Previous article: Automation Without Clarity Accelerates ConfusionNo page exists for this headline, so it is shown as artwork rather than a link.
• Next article: Choosing the Right AI Tools That Actually Move the Needle

Your business has a rhythm. We build the system around it.

From strategy to implementation, we design workflows that scale with you.

• Start a project
• Explore workflowsThe Workflows page is registered but is still a holding page rather than the real thing, so this is not made a link.