Issues help your team surface and solve problems, ideas, and opportunities using the IDS process. This guide covers how to create, prioritize, solve, send, and merge Issues in Strety, so nothing important gets lost between L10 meetings.

Issues represent problems, ideas, or opportunities that typically require input from others in order to be resolved. An example of an Issue could be an obstacle for someone on the team, a broken system, a missing step in a process, a customer complaint, or an employee grumbling.

Create new Issues from Quick Create or from a Team or Person Space's Issues page.

Give your Issue a Name and Description, then assign a Primary Space, Owner, Priority (if needed), Type, and Category (if needed), and add any Subscribers (if needed).

When you add a new Issue, Strety notifies only the creator and owner by default.

We recommend subscribing any additional users to the Issue or @ mentioning them in the description. This notifies those users and gives them a chance to review the Issue before your next meeting, so you spend less time getting everyone up to speed and more time on thoughtful, dialed-in discussion.

While running your L10, team, and 1:1 Agendas, you may find a problem you want to IDS, like an off-track Rock, a Measurable that missed its target, or a To Do that has been open for too many weeks.

We recommend creating an Issue directly from the problem item. This creates an opportunity for a more collaborative, contextual discussion as you work toward a proper response and resolution.

To create an Issue from an existing item, click the three-dot menu outside the item, then select Create Issue.

Or, click into the item and select Create.

Once you create the Issue, use the Related To link to see the original item the Issue is linked to.

You can also track all Issues created from an item within that item's modal.

Prioritize your Issues list in or before each L10 so the most impactful Issues are discussed and moved forward each week.

Here's a short video that demonstrates how to prioritize Issues for each meeting.

When you solve an Issue, don't just close it out. Add Solution Notes that detail what decisions were made to solve it.

Solution Notes are also included in meeting summary emails, so we encourage you to add Solution Notes during your meetings, not after.

An Issue must always have a Primary Space, which can be a Team Space or a Person Space. To learn more, read Strety Spaces | Complete Guide.

Each Issue can only be assigned to a single Team Space. When you create an Issue, Strety notifies only the creator and owner. To notify anyone else, subscribe them during creation. Once the Issue is created, all members of the Primary Space can see it.

You can also add Issues privately to a Person Space, where they serve as topics in 1:1 Agendas. For more on 1:1 Agendas, read Strety 1:1s | Complete Guide.

We recommend creating Personal Issues for any one-off or ad hoc topics that represent questions or challenges. This lets you add Solution Notes and assign linked To Dos to the Issue, which increases accountability and adds context.

Certain Issues may require another team's involvement to fully resolve them. In these cases, Strety makes it incredibly easy to send the Issue elsewhere and remain informed of any new activity or changes to its status, including when it's solved.

To send an Issue to another team, open the Issue and click Send to Other Team. Below, you see an Issue that began on the Leadership team that we now want to send to the Success team to resolve.

Issues sent from other teams have a tag that clearly identifies where they came from:

To review the current status of any Issues sent to other teams, click the Sent to other teams filter.

Click into the Issue to see whether it has been resolved and any commentary or Solution Notes added.

When the receiving team solves an Issue you sent, Strety notifies members of the original team. The notification includes the Solution Notes, so your team can see what was decided without opening the Issue.

To control where you receive notifications, see Strety Notifications Settings.

Have you ever added an Issue only to see there's already one (or several) about the same root issue? Strety makes it easy to merge Issues, so your team can combine fragmented context and reduce duplicate resolution efforts.

To merge Issues:

The merged Issue shows a Related To link, so you can view details from any merged Issues.

Check out Strety Reports for more insights and summaries of all Issues you have visibility into:
​

Want to learn more? Check out these Issue resources from Strety's Blog: