Kaizen Teams

Dropdown
Dropdown arrow for the table of contents.

Table of Contents

Clock icon for reading time.
Time to read

·

12

Calendar icon for the publish date.
Published on

·

December 19, 2024

Refresh icon for the last updated date.
Last updated on

·

August 18, 2026

Bruno Bologna, CEO at Kaizen Softworks

Bruno Bologna

LinkedIn icon.

Chia seed alchemist

CEO

About Us

About Us

Celebrating 10 Years of Kaizen Softworks: Words from Our CEO

Calendar icon for the publish date.
Published on

·

August 18, 2026

Refresh icon for the last updated date.
Last updated on

·

August 18, 2026

Clock icon for reading time.
Time to read

·

12

Bruno Bologna, CEO at Kaizen Softworks

Bruno Bologna

LinkedIn icon.

CEO

Last December 1st we celebrated our 10-year anniversary. Reaching a milestone like that is no small feat. It’s a moment to pause, reflect, and celebrate the journey we’ve taken together. Today, I’m honored to share some personal reflections, as I addressed our team during our celebration party.

Reflections on 10 Years

Today, I want to share some thoughts that came to mind when I was asked to say a few words at this very special event. Ten years don’t come around every day, and I think it’s worth taking a moment to look back.

When I started thinking about these 10 years, so many memories came flooding in—different kinds of memories. From client conversations to the time I got thrown into a pool. And, of course, many anecdotes that are now immortalized on Kaizen’s t-shirts, full of boldness and humor.

I also reflected on how we’ve grown—through crises, the pandemic, and challenging moments—and how we navigated those challenges together.

I won’t dive into every single memory, but I felt the need to categorize them, to see what they tell us.

Key Elements That Define Us

Through this exercise, I noticed that while our journey has been diverse, certain elements consistently stand out and define us as a company. I grouped them into four categories:

  1. Value Perceived by Our Clients: They choose us because they perceive something different in what we do—something that genuinely adds value.
  2. Value Perceived by Our Team: What do our team members take from their experience here? What do they tell a colleague when describing where they work? This can be ‘measured’ in many ways, but ultimately, it’s about that perception.
  3. Structure and Horizontal Approach: We constantly seek alternative ways to organize ourselves, questioning traditional methods to find what works best for us.
  4. Continuous Improvement: As our name suggests, there’s always a better way to do things. And when the investment is worth it, we go after those improvements.
  5. Our Culture: A space where respect, collaboration, and humor take center stage.
  6. Growth: Not just in numbers, but in quality and the impact we generate—our ability to influence clients and continue growing both inside and outside the company.

The Common Thread: Being “Different”

What ties these categories together? It’s not about being better or worse but about reflecting our priorities and how we do things.

If I think about what these categories have in common, the word that comes to mind is different. At Kaizen, we don’t strive to be different just for the sake of it—it’s our priorities and values that naturally lead us in that direction.

This difference is not better or worse, but it’s ours. It’s reflected in how we build relationships, how we think about solutions for our clients, and how we work together.

What We Want to Protect

What do we want to protect at Kaizen? We want to protect our relationships and our ability to make a positive impact.

Our relationships with clients, where trust and respect are our top priorities. And our internal relationships, where we aim to create an environment that allows us to grow as professionals and as people.

This focus on relationships is reflected in their longevity. It’s easy to measure how long a relationship lasts, and we’ve seen and measured this over the years. But longevity isn’t the only thing that matters—it’s also about the depth of those relationships and what they leave behind.

A Personal Reflection

For me, Kaizen has been so much more than a workplace. It’s been a space for learning, challenges, and personal growth. The last 10 years have transformed me not only as a professional but also as a person. And as part of this personal reflection, I invite you to ask yourselves:

What do you take away from Kaizen?

How do you imagine Kaizen 10 years from now?

Where can we go together?

I’m confident that the future we build will be as unique as the journey we’ve taken so far. Thank you for being part of co-creating this story.

And as a small example of what makes us different, would it be possible to sing ‘Happy Birthday’ the Kaizen way?

Last December 1st we celebrated our 10-year anniversary. Reaching a milestone like that is no small feat. It’s a moment to pause, reflect, and celebrate the journey we’ve taken together. Today, I’m honored to share some personal reflections, as I addressed our team during our celebration party.

Reflections on 10 Years

Today, I want to share some thoughts that came to mind when I was asked to say a few words at this very special event. Ten years don’t come around every day, and I think it’s worth taking a moment to look back.

When I started thinking about these 10 years, so many memories came flooding in—different kinds of memories. From client conversations to the time I got thrown into a pool. And, of course, many anecdotes that are now immortalized on Kaizen’s t-shirts, full of boldness and humor.

I also reflected on how we’ve grown—through crises, the pandemic, and challenging moments—and how we navigated those challenges together.

I won’t dive into every single memory, but I felt the need to categorize them, to see what they tell us.

Key Elements That Define Us

Through this exercise, I noticed that while our journey has been diverse, certain elements consistently stand out and define us as a company. I grouped them into four categories:

  1. Value Perceived by Our Clients: They choose us because they perceive something different in what we do—something that genuinely adds value.
  2. Value Perceived by Our Team: What do our team members take from their experience here? What do they tell a colleague when describing where they work? This can be ‘measured’ in many ways, but ultimately, it’s about that perception.
  3. Structure and Horizontal Approach: We constantly seek alternative ways to organize ourselves, questioning traditional methods to find what works best for us.
  4. Continuous Improvement: As our name suggests, there’s always a better way to do things. And when the investment is worth it, we go after those improvements.
  5. Our Culture: A space where respect, collaboration, and humor take center stage.
  6. Growth: Not just in numbers, but in quality and the impact we generate—our ability to influence clients and continue growing both inside and outside the company.

The Common Thread: Being “Different”

What ties these categories together? It’s not about being better or worse but about reflecting our priorities and how we do things.

If I think about what these categories have in common, the word that comes to mind is different. At Kaizen, we don’t strive to be different just for the sake of it—it’s our priorities and values that naturally lead us in that direction.

This difference is not better or worse, but it’s ours. It’s reflected in how we build relationships, how we think about solutions for our clients, and how we work together.

What We Want to Protect

What do we want to protect at Kaizen? We want to protect our relationships and our ability to make a positive impact.

Our relationships with clients, where trust and respect are our top priorities. And our internal relationships, where we aim to create an environment that allows us to grow as professionals and as people.

This focus on relationships is reflected in their longevity. It’s easy to measure how long a relationship lasts, and we’ve seen and measured this over the years. But longevity isn’t the only thing that matters—it’s also about the depth of those relationships and what they leave behind.

A Personal Reflection

For me, Kaizen has been so much more than a workplace. It’s been a space for learning, challenges, and personal growth. The last 10 years have transformed me not only as a professional but also as a person. And as part of this personal reflection, I invite you to ask yourselves:

What do you take away from Kaizen?

How do you imagine Kaizen 10 years from now?

Where can we go together?

I’m confident that the future we build will be as unique as the journey we’ve taken so far. Thank you for being part of co-creating this story.

And as a small example of what makes us different, would it be possible to sing ‘Happy Birthday’ the Kaizen way?

Related Articles

View all articles

·

Nov 4, 2026

SmartSense Live 2026 | Food Safety Summit

SmartSense LIVE26 recap: SmartSense ONE’s launch, the Disruptive Technologies acquisition, AI assistant KAI, and what it means for food safety and compliance teams.

Clock icon for reading time.

12 read time

Read more

SmartSense LIVE26 recap & takeaways

SmartSense LIVE26 took place October 7-9, 2026, at the Hyatt Regency Austin in Austin, Texas. The conference focused on food safety, compliance, and the role of connected technology in daily operations.

It was our first time attending LIVE, in the first year the conference opened to the wider industry. For us, it was also an opportunity to sponsor and support SmartSense, a company we’ve worked with since 2019.

Event details
Dates October 7–9, 2026
Venue Hyatt Regency Austin, Austin, Texas
Organizer SmartSense by Digi
Access October 7–9 for SmartSense customers; October 8–9 for industry attendees
Price $215.42 for industry attendees

Who SmartSense LIVE26 is for

SmartSense LIVE is designed for people responsible for safety, compliance, and operational performance. Its audience spans food service, healthcare, logistics, and other industries where monitoring physical conditions is part of everyday work.

That makes it relevant to operations and food safety leaders, as well as the technology teams supporting them. A monitoring system has to fit how people check conditions, respond to issues, and document what happened.

SmartSense LIVE26’s attendees spanned retail, healthcare, food service, and education, including Costco, CVS Health, and honeygrow. Speakers brought perspectives from operations, food safety, compliance, IT, and procurement.

What SmartSense LIVE26 was like

The main focus of the event were the SmartSense ONE presentation and the acquisition of Disruptive Technologies, which gave us a clearer picture of the company’s direction: connecting what happens in physical environments with the decisions and tasks that follow.

SmartSense ONE

SmartSense ONE brings SmartSense and Jolt capabilities into a modular platform with shared data and a common web and mobile experience, including offline support. Its seven modules cover monitoring, daily tasks, food safety, audits, maintenance, labeling, and staff scheduling. Customers can choose the capabilities they need and combine them as their requirements grow.

The focus extends from collecting data to acting on it

SmartSense describes its approach in three stages: Sense, Understand, and Act. Sensors capture conditions in the physical world, analytics and AI interpret the data, and digital workflows help teams respond.

The DT acquisition will strengthen sensing and expand SmartSense’s reach

On October 1, Digi announced an agreement to acquire Disruptive Technologies for $130 million. DT brings proprietary sensor technology, more than 250,000 deployed sensors, and devices designed to operate for up to 15 years. The acquisition would bring that technology into SmartSense, establish a stronger commercial presence in Europe, and expand opportunities in building automation and space occupancy.

Seven years of working with SmartSense

Our relationship with SmartSense began in 2019. Since then, we’ve worked together on product development and modernization as the company has grown and brought acquired products into its ecosystem.

One part of that work involved modernizing a remote monitoring app while incorporating features from other legacy products. The decisions went beyond rebuilding screens: we had to understand which workflows to keep, improve, combine, or retire. The resulting application serves more than 10,000 supply chain teams.

We’ve also worked on the process behind sensor deployments. A mobile installation app brought scanning, assignment, validation, and data synchronization into a guided workflow, helping technicians complete more deployments without adding headcount.

That work gave us a specific reason to be at LIVE: to hear from the people whose routines these systems support, and understand where software could make their work easier.

At our booth, we shared a demo showing how connected systems can work together in practice, along with our AI Adoption Handbook and some swag.

After Austin

Thank you to the SmartSense team for having us as sponsors and for the work we’ve shared across products and teams since 2019. Being part of LIVE added a new setting to that relationship: spending time with the people and organizations those products support.

And thank you to everyone who stopped by our booth, tried the demo, or took the time to tell us about their work.

If there’s a workflow you’d like to explore further, get in touch with us. We can help you clarify the problem and decide what would be useful to test first.

‍

·

Oct 23, 2026

How to build high-fidelity prototypes with AI

How a design system lets Marketing and Product teams use AI to build on-brand prototypes, based on Kaizen’s own experience and turnaround numbers.

Clock icon for reading time.

12 read time

Read more

AI makes it easier for more people across a company to create a first visual version without relying on Design for every step.

Marketing can generate campaign assets. Product managers can turn ideas into prototypes. Teams can make an idea visible earlier in the process.

That creates a new design problem.

If more people can create, how do you make sure the output still reflects the decisions Design has already made about hierarchy, typography, spacing, composition, and brand?

A design system can help.

When its rules, components, templates, and examples are available to AI tools, other teams can create within boundaries Design has already defined.

Design does not have to build every first version. It can focus on reviewing important decisions and improving the system when recurring problems appear.

A design system can carry judgment beyond the Design team

A design system gives teams shared rules for creating consistent work.

It can define:

  • Color, typography, spacing, and composition.
  • Components and how they behave.
  • Templates for recurring layouts.
  • Examples that show how those decisions work together.

That context is useful for AI too.

Without it, someone creating a page, presentation, or social post has to explain what “on brand” or “well designed” means in a prompt.

With a design system, many of those decisions are already documented. AI has a reference for how content should be structured, which components belong together, and what kinds of compositions fit the brand.

Teams get a starting point that is closer to the company’s existing visual language without having to describe it from scratch.

What this can look like across teams

Marketing can create recurring assets with less production dependency

Marketing often works with recurring formats such as social posts, campaign pages, and event assets.

Templates can give the team enough structure to create a usable first version independently. A social template, for example, can define typography, spacing, image treatment, and composition while leaving room for the content to change.

Design can then focus its review on the decisions that need attention.

Product teams can make ideas visible earlier

Product managers often need something visual before they need production-ready design.

If an AI tool has access to the same components and rules the product already uses, a PM can create a rough prototype that is closer to the real product than a generic wireframe.

The prototype is not a design direction by itself. It gives Product and Design something concrete to discuss.

Instead of spending time explaining what an idea might look like, they can focus on whether the flow makes sense, what needs to change, and where deeper design work is needed.

Generated work can show where the system is weak

AI does not only use the design system. Its output can also reveal where the system needs more guidance.

We saw this while using our own design system with AI at Kaizen.

Our Design team created the system while redesigning the Kaizen website. It documented the site’s colors, typography, composition rules, components, and templates. Marketing later began using that same system with AI to create website prototypes and social content.

One pattern kept appearing.

The AI put almost everything inside boxes.

Text, images, and entire sections appeared inside containers, even when a more open composition would have worked better.

Design reviewed the source material and found that many of the examples and rules leaned toward contained compositions. The AI was reproducing the patterns it had been given.

The team added guidance and examples for other layout approaches. The generated work became more varied and used more open compositions.

Instead of correcting the same problem in each new asset, the team improved the guidance that influenced future outputs.

That is one of the useful side effects of this process: recurring corrections can point to gaps in the system itself.

Autonomy still needs boundaries

Giving more people the ability to create does not mean every deliverable should follow the same workflow.

A recurring social post built from an established template may only need a quick review. A new product workflow may need much more involvement from Product and Design before anyone treats the prototype as a direction.

Teams can start by agreeing on three things:

What can teams create independently?

Identify recurring formats where the main design decisions are already understood.

What needs Design review?

Decide which outputs need a light check and which need deeper involvement.

What should go back into the system?

When the same correction happens repeatedly, update the shared rule, component, template, or example.

These boundaries make it clear where teams can move independently and where Design’s judgment is still needed.

What this changed for us at Kaizen

Before introducing this process, a LinkedIn visual could take more than two weeks from request to delivery once other priorities, coordination, review, and revisions were included.

We now estimate that a similar piece can move from copy to something ready to publish in about one afternoon.

For website work, a process that previously took around two weeks can now start with a Marketing-generated prototype in about two days, followed by roughly two days of Design refinement and production.

These are elapsed turnaround estimates, not active design hours. Reusable templates, the design system, clearer responsibilities, and the review process all contribute to the difference.

The biggest change is where the work starts.

Marketing can reach a concrete first version sooner. Design can spend more time refining important decisions and improving the system that will influence the next piece too.

For teams exploring this approach, start with one repeatable format.

Define the rules, examples, and templates needed to create a reasonable first version. Agree on where Design should enter the process. Then pay attention to recurring corrections.

If the same typography, layout, or composition problem keeps appearing, improve the shared guidance instead of fixing the same issue every time.

The goal is to make Design’s decisions reusable while keeping Design involved where its judgment matters most.

If you are working through the same questions, we can help you turn your existing design decisions into practical rules, templates, and review workflows your teams can use with AI.

‍

llms.txt