Blog

If you’re a product leader that is considering building or buying custom software solutions for your organization, you need to consider the total cost of ownership before moving forward. This article will help you be aware of the often overlooked costs of ownership for software, including cultural and employee role changes, re-training employees, lost productivity for a short period, and more that will be required to fully recognize the value of your software assets.

Learn what a product team is, why you should keep product teams small, and the key differences between integrated product teams and more traditional technology departments.

Product managers know – or a have likely heard – that psychological safety is an important element to their jobs. The concept has risen in popularity over the past several years as organizations are focusing ever more intently on culture and the work environment. But what does it mean or look like in practice for product managers? What’s the real value of psychological safety?

Learn how internal enterprise software can boost your employees’ fulfillment while simultaneously freeing up their time to explore more valuable areas of work.

In this blog, I walk through 7 different elements of the design of Insanity and apply it directly to productive, high-functioning teams. In summary, healthy teams are aware of the following: a clear end goal, micro-goals, times of occasional rest, next steps, workload & effort. They also have a visible team and a capable leader.

Since they pulled the plug on our local developer conference, we threw our own internal dev conference remotely: Crema DevConf 2020! In this article, we'll share some details about the event as well as an outline of our process for planning and execution. Our steps can be easily modeled by other dev teams that are looking for ways to further their craft skills and knowledge.

We’ve worked to define what it takes to craft a team of individuals that are truly passionate about learning. What we’ve found is that you must work to make it a habit. It requires a continuous “loop” of attention, testing, and reflection. This article will cover our approach to learning and adaptation.

In early June of 2020, a group of highly-ambitious digital product designers at Crema set out to complete an entirely-remote design challenge. The event was the first of its kind at our organization and one that allowed the designers to flex their creative muscles. In just one, 7-hour work-day, each designer sought out to create the UI screens for their own original app concept. And the results were pretty astonishing.

In February of 2020 Designer Mary Carnes decided to take a trip to Copenhagen to work for Crema abroad. It was both a means to scratch her adventurer’s itch as well as an opportunity to test whether our results-based culture would stretch across the globe and allow her to effectively work in a new environment. Mary share's her experience and tips on how to be successful working remote.

We often get asked about our company culture. From the outside looking in, our results-based culture (RBC) might look radical. Crema Test Engineer Ashley Holbrook breaks down what it's like to work in a flexible work environment and the positive changes it's had on her work and her personal life.

Learn why measuring the ROI of your software projects is so imperative to get buy-in and track progress. Plus how to leverage our software ROI calculator with different software types.

Your team's North Star is an orientation aid that helps you understand where you are and set your instruments for the journey. Learn how to calibrate your team for the road ahead with this template.