Product. Culture. Code.

The right product

A wonderful culture

A solid codebase

The Keys of a great product, culture and code does not come by accident. It's built consciously, over time, and with intent. A concept that we have practiced, tested, adapted and constantly improved. So you can have the right keys to unlock the right doors -- when they're needed

It is what we're about.

Sometimes you just need a room unlocked, other times it's unlocking every single one of them. Lots of keys to open a lot of doors. Some are for starting out, others are far more advanced and complex. Each keyring is different just like every company, every product and every codebase. Let's open some doors for you, discover the right product, deliver great code, and build a strong culture.

We get things done.

A lot of people talk product, a lot of people talk code. We do all 3. From customer interviews to sitting next to your development team writing code, it's why were different and why we get results.

I worked with [Rileytech] during Dojo sessions back in 2019. His passion and commitment to the Teams is outstanding. Jesse is a conscientious and thorough Dojo Technical Coach. He encouraged team members to follow many best practices like TDD where he emphasized 100% code coverage in JUnits for functional requirements and exception handling. He is very easy to work with and is a true team player. He would make a great addition to any organization




Discover and challenge your assumptions ...then back it up with data and behaviors



From hiring to team building, facilitation, retros, space hacking, employee engagement. Curate your culture.

SOLID principles


From unit/micro to UI/smoke, build a foundation of technical excellence that are both practical and tactical

Recent Articles

Is Luck a dirty word?
product key advanced image

How do you use the phrase "I was lucky"? I've noticed how I use it, and I realized I was indeed using it to cover up various things.

Yes, you should test logging statements
product key intermediate image

Code is um, code, so yes, you should test logging statements. It'll not only demo why you thought it was important, but give someone else a chance if something does go wrong. Otherwise, continue to scroll-scroll-scroll-scroll

Navigating Crisis - Create a Wartime Roadmap
product key fundamental image

Everything has went sideways with the pandemic and it's left many companies scrambling - how they did business is no longer how you do business now what?