How product managers use Zepel

Zepel lets you go from customer requests to shipped software painlessly.

In this cycle of “going from requests to shipped software”, Zepel lets product managers to consolidate feedback from several customers from multiple sources, prioritize them, and align the squad on the prioritized outcome. And developers turn these prioritized outcomes into usable software.

In this article, we’ll see how you, a product manager, can use Zepel to achieve this.

1. Consolidate requests from customers and prioritize

Your customers share feedback, request features, and report bugs from several sources. How do you consolidate all of them from multiple customers?

By connecting all the sources to Streams in Zepel, you can bring in first party data of the feedback, requests, and bugs under a single roof.

You can merge duplicates, filter and segment your requests, and finally prioritize them using custom tags.

Zepel Streams

2. Create a Squad for your team

As a product manager, you’d want to bring all the features your team will be working on under one single squad.

A squad in Zepel is usually named after a product or an initiative, such as Web App or Android or iOS.

All Squads in Zepel

You can collaborate members of your squad who will be working on your prioritized customer feedback.

Learn how to create a squad →

3. Delegate prioritized features to a squad

Now that you’ve prioritized your features, created a squad, and collaborated with members of your squad, you can now delegate your prioritized requests to the squad.

You can do this by linking the request to a feature or an item in the squad.

You’d link your request to an item if you’re working on bug fix or if the request requires you to complete a small task. If your customer requested a feature, then you’d link it to a new feature.

Once linked, you’ll be able to see the feature’s progress from within the request. And when you open the linked feature or an item, you’ll see it’s linked to a request.

This enables you to track the progress effortlessly. And it helps your entire squad to get a context of why they’re building what they’re building.

4. Spec the Feature in detail

If you linked a prioritized request to a feature, it’s time to spec it in detail, so your development team doesn’t build unnecessary functionalities.

This is where items and its types come into play!

A Feature houses all items - user stories, tasks, subtasks, bugs, and enhancements.

Adding items for your feature is as simple as writing on a document. Simply hit enter to create another item. And press Cmd + Shift + S if you’re on a Mac (Ctrl + Shift + S on Windows) to toggle between item types.

Items and its types in Zepel

Use Descriptions to add more details to each work item. For example, product managers use description as a place to add acceptance criteria for user stories and attach files below it to share files for further references.

These items can be collaboratively worked together by your squad using either a Sprint or a Kanban Board. Developers can streamline their workflow using deep GitHub, Bitbucket, and GitLab integrations among many others.

Ready to plan and prioritize features effortlessly?

Try Zepel for FREE See other use cases

Further Reading