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.

In both instances, Jesse has excelled at being sharer of knowledge and compiler of group knowledge to facilitate new knowledge. Jesse is always my first phone call when I am researching or beginning any tech related project. He is a valued member of my team and he will be the star of any team that is fortunate enough to have him.

Daniel Shaw, GunMag Warehouse, USMC Retired

Services

Product

Product

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

Culture

Culture

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

SOLID principles

Code

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 which got me thinking - is luck a dirty word?

Meeting overload? Include outcomes
product key fundamental image

Agendas are a good start, but how do you know the meeting was useful? I started to think about how I could make a meeting effective by applying the same method I use for product development - How will I know it's on the right path? Come up with a metric.

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

Contact us

Think you could use our help or just have a question? Send it here!

;