Skip to content
Tallyfy
Developers

Integrating Agile and Design Thinking into process improvement

How can Agile and Design Thinking accelerate improvements?

Section titled “How can Agile and Design Thinking accelerate improvements?”

Traditional improvement projects can run for months while the team waits for perfect data. By the time a fix ships, people have lost momentum, or the fix only treats a symptom of the real problem.

Agile breaks the work into short sprints, so changes reach people in weeks instead of at the end of one long project. Design Thinking decides which changes to try by starting from what customers and staff actually experience, and Lean Six Sigma’s measurement then tells you whether each change worked.

Agile principles that transform improvement projects

Section titled “Agile principles that transform improvement projects”

An improvement sprint usually lasts one or two weeks, and each one should end with a change that’s live in the process.

Sprint-based delivery: The first sprint might fix the most obvious bottleneck and the second might simplify a handoff between two teams. A third could add a Tallyfy automation that assigns a routine step based on a form field answer, so nobody routes it by hand. What you learn in one sprint decides what the next one tackles.

Daily standups for improvement teams: Replace weekly status meetings with 15-minute daily check-ins where each person says what they finished yesterday, what they’re working on today, and what’s blocking them. Blockers then come up within a day instead of waiting for the next weekly meeting.

Kanban boards for visual management: Put each piece of improvement work on a board with columns such as “To Do,” “In Progress,” “Testing,” and “Done.” Anyone can then see what’s moving without asking for a status report. Tallyfy’s Tracker does something similar for the processes themselves: its Board view shows each running process as a card with its progress.

Minimum Viable Improvements (MVI): Look for the smallest change that helps, such as reordering two steps in a template. You can make it in a day instead of waiting for a full process redesign.

Design Thinking: beyond optimization

Section titled “Design Thinking: beyond optimization”

Lean Six Sigma improves the process you already have. Design Thinking asks whether that process serves the customer at all, and changes the question from “How do we fix this process?” to “How might we delight our customers?”

The five stages in process improvement:

  1. Empathize: Find out what the process is like for the people in it, beyond what the metrics show. You might shadow customer service reps for a day or listen in on customer calls.

  2. Define: Reframe problems from the user’s perspective. Instead of “Reduce processing time,” ask “How might we give customers confidence their request is progressing?”

  3. Ideate: Collect as many ideas as you can before judging any of them. Build on each other’s suggestions with “Yes, and…” instead of shooting them down. Ambitious ideas belong here, such as letting customers track a request the way they track a pizza delivery, or having AI catch common errors before they happen.

  4. Prototype: Build the cheapest version people can try, such as a paper sketch of a new form or a rough Tallyfy template with the new steps and form fields. A few people can launch a template version as real processes before you spend more on the idea.

  5. Test: Watch real users work through the prototype, note where they get confused and what they like, then change it and test again. If those users are customers or suppliers, assign them the step as guests, who complete it from an email link without a Tallyfy account.

Practical integration strategies

Section titled “Practical integration strategies”

Start with Design Thinking for complex customer problems: Journey mapping, which follows a customer through every step, can show a frustration your metrics don’t track, such as not knowing whether a request is moving at all.

Apply Agile for rapid implementation: Once you’ve identified improvements through DMAIC analysis or Design Thinking ideation, plan them as two-week sprints. Try each change with a small group first, for example on a copy of the template that only one team launches. Once it works, make the same edit to the main template.

Use Lean Six Sigma for fine-tuning: After Agile implementation, apply Six Sigma tools to measure results and identify remaining waste. When a change has proved itself, write it into the Tallyfy template so every process launched afterward follows it. Statistical analysis can also settle questions the sprints left open, such as the right team size or skill mix.

Creating psychological safety for innovation

Section titled “Creating psychological safety for innovation”
  • Celebrate intelligent failures: When an experiment doesn’t work, ask “What did we discover?” and treat the answer as a result of the sprint.
  • Time-box experiments: “Let’s try this for two weeks” feels safer than permanent change.
  • Start small: Try a change with one team, on a copy of the template, before rolling it out company-wide.
  • Share what you learned: Tell other teams about the experiments that failed as well as the ones that worked, so nobody runs the same test twice.

Tools and techniques that work

Section titled “Tools and techniques that work”

Rapid improvement events with Agile structure:

  • Monday: Understand current state (Gemba walk, data review)
  • Tuesday: Generate solutions (Design Thinking exercises)
  • Wednesday: Prototype and test top ideas
  • Thursday: Implement quick wins
  • Friday: Plan next sprint, share learnings

Design sprints for redesigning a process run over five days:

  • Day 1: Map the challenge and pick a target
  • Day 2: Sketch competing solutions
  • Day 3: Decide which ideas to prototype
  • Day 4: Build a realistic prototype in Tallyfy
  • Day 5: Test with real users

Scrum for continuous improvement teams:

  • Product Owner: Process owner who prioritizes improvements
  • Scrum Master: Guides the team and removes obstacles
  • Developers: the people who implement improvements. The Scrum Guide ↗[1] puts the whole Scrum team at typically 10 or fewer people
  • Sprints: 2-week cycles of focused improvement work

Using Tallyfy for agile improvement

Section titled “Using Tallyfy for agile improvement”

Rapid prototyping: Duplicate a template and test changes on the copy. The original template and the processes launched from it stay untouched.

Side-by-side testing: Launch some processes from the original template and some from the copy. To compare them, export each process to CSV and look at the task completion times.

Immediate updates: Edit a template and every process launched after that uses the new version, with no IT release. Processes already running keep the version they started with.

Continuous feedback: Comments on tasks capture improvement ideas in real time. To track the effect of a change over months, the Tallyfy Analytics add-on copies your process data to a private database that BI tools like Power BI or Tableau can connect to.

Common integration pitfalls

Section titled “Common integration pitfalls”

Analysis paralysis meets wild ideation: Time-box both the analysis and the creative phases, for example one week of data gathering and one week of ideation, and then start testing.

Agile chaos without Lean discipline: Rapid iteration still needs a standard, or “agile” turns into “anything goes.” When a change works, document it and update the Tallyfy template, which every newly launched process follows.

Innovation theater: Sticky notes and design workshops only count when they change how the work gets done. End each creative session by naming at least one specific change to a Tallyfy template and who will make it.

Forgetting the control phase: Short sprints make it easy to move on before checking that a change has stuck. Build measurement and control into every sprint, not just the end of the project. A CSV export of the processes launched before and after a change lets you compare their task completion times.

Example: blending the approaches on one process

Section titled “Example: blending the approaches on one process”

Take a customer onboarding process. Interviews and journey mapping might show that customers care as much about knowing where their request stands as about speed. A two-week sprint could then test status updates with a small group of new customers. In Tallyfy, you’d send each one a public link to their onboarding process, which shows its progress without a Tallyfy account. A Lean review removes steps that repeat work, and DMAIC’s measure and control phases check that onboarding times stay consistent after the change.

Section titled “Related articles”
Get in touch
About Tallyfy