Julien Calixte
@juliencalixte.bsky.social
Head of Engineering, making apps at Theodo Apps with lean thinking.
🇧🇷🇫🇷
🇧🇷🇫🇷
Made my first article on the Toyota production system! thinking-people-system.house with the pull system: thinking-people-system.house/pull-system
Explorable Thinking People System
Author: Julien Calixte,
My understanding of the Thinking People System and
how it helps people and organization to improve
thinking-people-system.house
May 12, 2025 at 8:34 PM
Made my first article on the Toyota production system! thinking-people-system.house with the pull system: thinking-people-system.house/pull-system
In "The Toyota Way of Dantotsu Radical Quality Improvement", QA teams don’t just report defects—they help teams address root causes. They empower, rather than take responsibility away. That's the true value of QA.
February 3, 2025 at 4:03 PM
In "The Toyota Way of Dantotsu Radical Quality Improvement", QA teams don’t just report defects—they help teams address root causes. They empower, rather than take responsibility away. That's the true value of QA.
And what about QA? Should we remove it entirely? No, but it can evolve: instead of just detecting defects, it can help improve quality within the flow.
February 3, 2025 at 4:03 PM
And what about QA? Should we remove it entirely? No, but it can evolve: instead of just detecting defects, it can help improve quality within the flow.
Identifying autonomy zones and ensuring that production & inspection happen in the same place is key in a healthy environment. Developers should be able to check if the product is ok.
February 3, 2025 at 4:03 PM
Identifying autonomy zones and ensuring that production & inspection happen in the same place is key in a healthy environment. Developers should be able to check if the product is ok.
The downside is that it creates a bad reinforcing loop: the more QA is present, the less developers take ownership of quality—leading to an even greater need for QA. 🔄
Adding lead time in rework and lack of focus for everyone.
Adding lead time in rework and lack of focus for everyone.
February 3, 2025 at 4:03 PM
The downside is that it creates a bad reinforcing loop: the more QA is present, the less developers take ownership of quality—leading to an even greater need for QA. 🔄
Adding lead time in rework and lack of focus for everyone.
Adding lead time in rework and lack of focus for everyone.
I couldn't agree more. I've seen many projects where QA and devs can't stand each other, forgetting why they are working in the first place. (That’s why I wrote an article to raise awareness about better team synchronization, feel free to check it out thinking-people-system.house/pull-system)
Exploring Pull System
Author: Julien Calixte,
My understanding of how a pull system
can help team prioritize.
thinking-people-system.house
February 1, 2025 at 8:29 PM
I couldn't agree more. I've seen many projects where QA and devs can't stand each other, forgetting why they are working in the first place. (That’s why I wrote an article to raise awareness about better team synchronization, feel free to check it out thinking-people-system.house/pull-system)