惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

美团技术团队
罗磊的独立博客
SecWiki News
SecWiki News
The Register - Security
The Register - Security
The GitHub Blog
The GitHub Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园 - 三生石上(FineUI控件)
S
Schneier on Security
IT之家
IT之家
博客园 - 聂微东
T
The Exploit Database - CXSecurity.com
Recorded Future
Recorded Future
大猫的无限游戏
大猫的无限游戏
Know Your Adversary
Know Your Adversary
Latest news
Latest news
Vercel News
Vercel News
G
GRAHAM CLULEY
D
DataBreaches.Net
D
Darknet – Hacking Tools, Hacker News & Cyber Security
S
SegmentFault 最新的问题
博客园_首页
雷峰网
雷峰网
T
Tenable Blog
Spread Privacy
Spread Privacy
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
酷 壳 – CoolShell
酷 壳 – CoolShell
Cisco Talos Blog
Cisco Talos Blog
V
Visual Studio Blog
J
Java Code Geeks
博客园 - Franky
The Cloudflare Blog
Apple Machine Learning Research
Apple Machine Learning Research
C
CERT Recently Published Vulnerability Notes
T
Threatpost
Google DeepMind News
Google DeepMind News
F
Fortinet All Blogs
P
Privacy International News Feed
T
Threat Research - Cisco Blogs
T
The Blog of Author Tim Ferriss
V
Vulnerabilities – Threatpost
Recent Announcements
Recent Announcements
Blog — PlanetScale
Blog — PlanetScale
Security Latest
Security Latest
U
Unit 42
M
MIT News - Artificial intelligence
Y
Y Combinator Blog
K
Kaspersky official blog
有赞技术团队
有赞技术团队
B
Blog
腾讯CDC

Agile Alliance

Is Agile Coach Camp for You? | Agile Alliance The Underrated Skill of Intentional Observation | Agile Alliance From Requirements to Results: A Product‑First Model for Business Analysis | Agile Alliance Two Steps Ahead: What I Learned by Leading an AI Adoption Before Anyone Asked Me To | Agile Alliance Case Study: When a Security Rollout Became a Design Problem | Agile Alliance Call for Nominations: Agile Alliance Board of Directors (2027–2029) | Agile Alliance Breaking Eggs: The Case for Dropping Practices | Agile Alliance Reflections on the Digital Cleanup Gathering 2026 | Agile Alliance Case Study: Strengthening Scrum Master Leadership Through Scenario-Based Discussion | Agile Alliance Built for Change: Enterprise Agility Isn’t Optional Anymore | Agile Alliance Skilling Up Development Teams | Agile Alliance Case Study: When Agile Meets Neurodivergence | Agile Alliance 25 Years Ago, a Manifesto Was Born | The Agile Manifesto | Agile Alliance
Case Study: How Joy and Kaizen Helped Drive 16x Sales Growth | Agile Alliance
Joe Foley · 2026-05-14 · via Agile Alliance

This Agile case study is drawn from the Agile Experience Report “Joy, Inc. in Japan! How I Built a Joy Dojo in the Land Where Kaizen was Born” by Tadahiro Yasuda.


Tadahiro Yasuda, Creationline’s CEO, had reached a breaking point. Creationline, a Japanese IT company, had grown, but its culture had not kept pace. Communication between teams was poor. Employees were unmotivated. Teams argued and disrespected one another. A major client project went into crisis, requiring late-night response meetings. Some engineers became ill and left.

The deeper problem was not simply workload or effort. Creationline lacked shared direction, trust, and clear communication. Yasuda later recognized that he had contributed to the problem by focusing too heavily on immediate sales and profits while assuming employees understood the company’s purpose without it being clearly stated.

The Challenge

Creationline began as a contract IT services company. Its work depended on accepting client software development requests, building solutions, and delivering them. Yasuda believed that if the company pursued revenue, satisfied customers, and stabilized the business, employees would eventually become happier.

That assumption failed. Employees did not understand the company’s vision, goals, or direction. Teams acted from their own assumptions. Because they did not understand one another’s work, conflict grew. Motivation dropped, delivery suffered, and the company’s reputation was damaged.

The company also faced a cultural constraint. In Japan’s high-context business environment, people may assume that intent can be understood without being stated directly. Yasuda came to see that this was not enough. Vision and philosophy had to be made explicit.

The Approach

Creationline did not respond with a single framework rollout. Its change unfolded through a series of experiments. The company treated culture as something to inspect, improve, and adapt over time.

The approach drew on Kaizen (continuous improvement through small, ongoing changes) and several Agile-compatible practices:

  • Clarifying purpose: Creationline updated its philosophy to HRT + Joy: Humility, Respect, Trust, and Joy.
  • Improving transparency: The company began sharing more internal information, including financial information where appropriate.
  • Visualizing work: Teams learned from Kanban, retrospectives, and Value Stream Mapping.
  • Investing in shared learning: The company paused operations for team-building and learning activities.
  • Adapting ideas from Joy, Inc.: Inspired by Menlo Innovations, the company featured in the book Joy, Inc., Creationline experimented with pair programming, daily standups, project reviews, free seating, family-friendly policies, and selected ideas for reducing hierarchy.
  • Building human connection: The company introduced practices that helped employees praise, understand, and connect with one another.

Implementation and Iteration

Creationline’s first attempt to improve communication was a monthly in-house social gathering. The effort eventually failed. Yasuda had not clearly explained the purpose, had not shown enough commitment to changing the company, and had not improved the event over time.

The company then began reshaping its company-wide meetings. At first, these meetings focused on project progress. But because trust was low, employees did not share concerns or problems. Yasuda changed the format and began using the meetings to discuss what kind of company they wanted to become and how work could become more joyful.

Creationline also learned from outside examples. After visiting a company that used Kanban across departments, some teams began using retrospectives, Kanban visualization, and Value Stream Mapping. Seeing the practices in use helped create shared language.

The company later invested in a full-company team-building workshop with support from an Agile coach. Afterward, some employees voluntarily formed a Kaizen team to address internal problems.

As Yasuda adapted ideas from Joy, Inc., a book about Menlo Innovations’ people-centered way of working, the company introduced more collaborative practices. These included pair programming in some projects, greater information transparency, daily standups, project reviews, free seating, and family-friendly policies.

Two practices became especially important for connection. Furu-Furu Relay Talk, a structured public praise activity, gave employees a way to recognize colleagues in front of others. Zatsudan, a regular non-business conversation practice, helped people from different projects get to know one another. Over time, these practices helped strengthen cross-team relationships and psychological safety.

Results and Impact

Creationline reported significant business and cultural results during the transformation period. Sales increased 16 times, and profits increased 28 times. During the shift to remote work, office attendance dropped to 1.5 percent, yet the company achieved 130 percent of the previous year’s revenue.

Employee engagement scores increased after remote work began. The company also reported a client Net Promoter Score, or NPS, of 63. Its work with DENSO, a major auto parts supplier, became one example of applying Joy, XP-inspired development practices, and close customer collaboration to real projects.

By applying Kaizen to corporate culture, Creationline became more able to respond flexibly to environmental change. The broader impact was cultural as well as financial: the company became more transparent, more connected across teams, and more deliberate about building shared understanding.

Lessons Learned

  • Culture change cannot be copied. Creationline learned from other companies, but it had to adapt practices to its own context.
  • Leadership behavior matters. The transformation began when Yasuda recognized his own role in the company’s problems.
  • Purpose must be explicit. The company could not rely on implicit understanding. Vision, philosophy, and direction had to be stated clearly and repeatedly.
  • Trust takes time. Early meetings failed because people did not yet feel safe sharing problems. Trust had to be built through repeated action.
  • Kaizen applies to culture. Creationline improved culture the same way Agile teams improve work: by trying practices, observing what happened, and adjusting.

Key Agile Takeaways

  • Reframed culture change as iterative learning
    Creationline treated transformation as ongoing Kaizen rather than a one-time change program. This reflects Principle 12: teams regularly reflect and adjust their behavior.
  • Prioritized individuals and interactions
    Practices such as Furu-Furu Relay Talk and Zatsudan strengthened relationships before expecting better collaboration. This reflects the Agile value of individuals and interactions over processes and tools.
  • Used visualization to improve shared understanding
    Kanban and Value Stream Mapping helped teams see work and discuss problems more concretely.
  • Built trust through transparency
    Sharing information, including financial information where appropriate, helped employees understand the organization more clearly.
  • Supported motivated people
    The company invested in workshops, shared learning, and voluntary Kaizen teams. This reflects Principle 5: give people the environment and support they need, and trust them to get the job done.
  • Improved customer collaboration
    Creationline’s work with DENSO showed how internal culture change could support closer collaboration with customers. This connects to the Agile value of customer collaboration over contract negotiation.

Read the original Agile Experience Report “Joy, Inc. in Japan! How I Built a Joy Dojo in the Land Where Kaizen was Born” by Tadahiro Yasuda.