If you ever find yourself copying a task to reference it somewhere else, or wish a task can remain in a particular workflow but also be in another, Mirrors is the answer.

Here are some example of popular use cases for Mirrors to get your wheels turning. The possibilities are endless.

Cross-team Collaboration

When different teams work together, you may find that tasks don't always fall neatly under one umbrella or the other. Regardless, the work needs to get done. With Rindle, you can track tasks between teams with Mirrors, effortlessly, avoiding confusion and miscommunication .

As an example, both the Sales and Marketing teams may want to keep a pulse on a new feature page being added to the company website, but the Marketing team is responsible for making the change. In Rindle, you can Mirror the task in both the Sales board and the Marketing board using the Hub & Spoke Model, letting each team organize and prioritize how they see fit.

When Marketing starts working on it, Sales will be able to track the progress and be 100% in the loop, without ever leaving the Sales board and without any additional busy work.

Each Team can Work Differently

Sometimes large projects have many teams involved, and each team needs to see the projects tasks in their own workflow.

As an example, if you're building a new website, the design team might think of it on a page by page basis, while the back-end developers think of building the foundation and up from there.

In Rindle, each team can have a board with its own workflow and the tasks can be Mirrored on both boards. Since the tasks are the same, you’ll have a shared history between the teams that's instantly in sync, and details won’t get lost in the hand off.

Another added benefit of Mirroring tasks in more than one board is the freedom and flexibility you can achieve. You don't have to adapt to a single way of working or organizing your work. You can Mirror your assigned tasks from your shared boards to and individual board and have them process through your own private workflow.

Product Management Workflow

Sometime you have multiple boards in a workflow where a task will move from one board, to the next board, and so on. But often "moving" it from one board to another isn't what you actually want to do because you want the task to remain on the original board for context.

A great example of this is a product management workflow. Let's say you have a software development team and you have a simple product management workflow that looks like this:

  1. Feedback board - tracks customer feature requests
  2. Bugs board - tracks bugs found internally and by customers
  3. Roadmap board - features you plan to build
  4. Development board - features you are building

When feedback comes in from customers, including feature requests and enhancements, they get tracked on the Feedback board. As you prioritize and decide which features should go onto the product Roadmap to be queued for development, instead of moving the feature request off of the Feedback board and onto the Roadmap board, you can mirror it and put it in a list called On Roadmap. By doing this, you'll have a better understanding of feedback that your moving forward with, and who requested it, without having to jump around different boards and manually track stuff down.

Meeting Prep

The power of collaborating in Rindle should ultimately mean less meetings for your team, but it should also make your meeting faster, more efficient, and more focused on the work that matters!

For many teams, preparing for meetings means copying and pasting tasks, notes, and tidbits from emails to put together a meaningful agenda. Maybe it's time re-typing and piecing together information that will never be used again outside that meeting.

Whatever the process, it usually takes an unnecessary amount of time. Time that is wasted on "busy" work.

With Rindle, you can create a board for your agenda and Mirror previously created tasks from multiple related boards and projects. In the agenda you can organize them as needed, maybe by the order in which your discuss them, but in the original board they remain in their current workflow and priority.

The ability to Mirror tasks from multiple boards also means that items can quickly be added to agendas during a meeting. As a task is discussed with your team, you can click on it to pull up the description, sub tasks, and comments as if you were looking directly at the task on the original board. No jumping around, no copy and pasting, no double data entry. 

Include decisions made in the meeting directly into the task, which will automatically trickle out to the board for the project team to see. You can even assign the task, no follow-up emails or meeting summaries needed.

When everyone is referencing the same information, you can spend less time doing busy work and more time on the work that matters.

Priority Across Projects

When priorities are constantly shifting, it can be really tough for a team to wrap their head around what they should be doing when.

For example, you could have a team of freelancers that are working on writing, editing, and publishing content marketing assets. Freelancers may be rolling in and out of the production cycle based on their availability, level or commitment, or specialty.

With Rindle, you can create a board called Priority and Mirror tasks that are the highest priority on demand, as priorities shift throughout the day. This allows your team of freelancers to look at the priority board first when they are available to work on some content.

No meeting, no additional communication, no project specifics. Of course, the power of Mirrors allow those tasks to remain on their respective boards and workflows. As their status changes, it will be updated everywhere.

Meeting Notes & Tasks

If you attend regular meetings, usually one person is in charge of capturing notes and action items. After all, it doesn't make sense for everyone to waste time capturing and maintaining notes.

In Rindle, you can use a task to capture the meeting notes and action items (sub tasks) so everyone can have access to them. For example, the marketing team has a weekly meeting. After the meeting is over, the person responsible creates a task on the Marketing board in the Resources column, and create sub tasks for all the action items and assigns them to the appropriate people.

On one hand, you want to keep the tasks group under the meeting notes tasks in order to keep the context. It also makes it easier to quickly reference back to see where all the tasks are at, especially before the next meeting.

On the other hand, you want to move all of those tasks from the meeting through the standard Marketing board workflow, Backlog, In Progress, Blocked, Done. if you move the sub tasks off the meeting notes task, you instantly lose the context to the meeting.

In Rindle, you can Mirror the sub tasks into the Backlog list on the same board, keeping the task as a sub task of the meeting notes task, and allowing it to move through the Marketing workflow at the same time. As tasks get complete, they will automagically show as completed in the meeting notes as well.

Did this answer your question?