Home Developer Workflow management: removing “goals” feature

Workflow management: removing “goals” feature

Author

Date

Category

Building Codacy, we’ve learned a lot about how people want quality management throughout their workflow.

By listening to customers we’ve learned that the most important job of our product is to standardize quality in teams, departments and companies. Many lessons come about by looking at how people are using the product.

As such, today we’re killing our goals feature.

And the reason is simple: in the last month, only 50 people created a goal and while interest in the feature was good, usage was not.

Why did we create goals in the first place?

People use Codacy in two different ways. The first is to clean code as they commit/pull request. As Codacy identifies problems in code, people fix it. In other words: very actionable and easy to manage — as you create problems you fix them.

The Second is to identify all problems in a code base. While being very important, this is not actionable at all as what can you really do with the information that you have 50,000 quality problems in your code?

So what we tried to do with our Goals feature was to make this second component actionable by giving you easy to resolve insights that over time compound.

Why did it fail?

Goals was a first test into how could we “gamify” code quality.

We now know Goals failed because:

  1. Goals did not integrate well enough with neither other parts of the product nor other tools that help developers manage their day to day
  2. It wasn’t easy enough to use.

What’s next?

We really like the idea of helping you fix the unsurmountable amount of technical debt in your code base. As such, we’re still excited about this. We will revisit this feature in the future with a better understanding of what our users and customers want.

Thoughts? Feedback? Comments?

We can only do the right product if we learn from you. Tells us how you feel about this. How would a great Goals feature be?


About Codacy

Codacy is used by thousands of developers to analyze billions of lines of code every day!

Getting started is easy – and free! Just use your  GitHub, Bitbucket or Google account to sign up.

GET STARTED

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Subscribe to our newsletter

To be updated with all the latest news, offers and special announcements.

Recent posts

7 drawbacks of linting tools

Linting tools (also known as linters or static analyzers) help automate the code review process. They perform basic static code analysis by flagging programming...

Using the API to add Codacy Grade details to the Readme

Some context Codacy has a badge mechanism that can be included in your Readme file. It gives you an idea of the grade of your repository, from...

March Product Update: Support for Cloud Infrastructure-as-code, Custom Reports with API endpoints & more 🚀

Here are some fresh updates from March! This month we bring you a new product offering, new features, and product updates, interesting reads, and...

Top 10 ways to perform fast code review

We always want to be fast at code review.. How frequent is it for you to be reviewing code at 3am? When code reviewing, do you...

Interview with Gary McKay, Somos’ Director of Agile Service Delivery

Somos is a proven leader in registry management and data solutions. Somos fosters meaningful connections by delivering value, innovation and confidence to consumers. We...