How Event Modeling Can Transform Your Tech Team?

After a year of improving the product’s architecture and helping the team align with the business, the unexpected happened, and I got laid off.

Bad technical decisions might lead a company to increase its profit margins by eliminating people. It is a straightforward plan but exposes the company’s toxicity. How can employees trust to provide value to a company if the company sees us as liabilities?

It started with an event modeling session.

Understanding the system holistically gave a team of two people enough clarity to deliver the new functionality. Due to the project’s success, the company agreed to rewrite the product using event modeling as its foundation.

Getting laid off is shitty, yes, but that doesn’t mean that we can’t learn from the experience.

I realized that a significant amount of Ruby on Rails codebases are stuck with a combination of the following problems:

• They migrated to microservices without defining boundaries, and now implementing anything takes ages.
• They have a mix of random technologies that provide little value compared to the effort required to install or maintain them.
• People from the same team have different opinions about the business challenge and how technology affects it.
• Engineers are not involved in feature discovery, analysis, or modeling. They exist to execute top-down solutions.

Event modeling solves all these problems. It can identify opportunities to improve current operations.

If you think you have one of these problems, I can help; let’s talk.