DoubleLoop lets you populate your strategy map stats via your data warehouse. Now we integrate with Amazon Redshift.
When you make a change to a metric source, you can now click "run" button to update the stats on your strategy map for any associated metrics.
You can now indicate who's responsible for each workstream.
Something magical happens when teams have clear data-driven feedback loop.
Here's how it works:
(1) Identify a high-leverage input metric for an initiative.
(2) Create a Slack channel for that initiative and invite the team.
(3) Use DoubleLoop to send the metric data to Slack at the frequency of your choosing (daily, weekly, etc.).
Now, everyone on the team will have a shared understanding of the results of the work. They can celebrate wins and make necessary adjustments when things are headed in the wrong direction.
Companies have different time horizons. Some companies obsess over their metrics daily while others look quarterly. For a consumer marketplace "long-term" might mean 6 months. For a car manufacturer, it means 10 years.
Consequently, one of our most frequent feature requests is to customize the time intervals that appear on our strategy maps.
By default, we show your performance for the last 7 days, 6 weeks, and 12 months. These are the time intervals that Amazon uses to look at their retail business. But now you can customize it to whatever is right for you.
Our new CSV upload tool is a great way to get lots of metric data into DoubleLoop without integrating your tools or using our API.
You can use it to make a proof-of-concept map or as a regular workflow for importing data.
Quickly delete connections on your map by clicking the connection to select it and then hitting "delete" on your keyboard.
A strategy is based on assumptions. We're making it easier to judge the strength of your assumptions with "correlations scores" between metrics. For example, we show you how correlated or uncorrelated your input metrics are with your North Star metric.
The correlation scores are between -1 and 1. "1" means perfect correlation and "-1" means inverse correlation.
If your North Star is inversely correlated with a business KPI, you probably need a different North Star.
Minor updates
Minor updates
Now you have much more control over which metrics you can pull into DoubleLoop from Google Analytics. You can configure the property, metric, and segment for each metric.
When you're visually communicating your product strategy, details matter. Now you can manually adjust the position of nodes on your map to organize it exactly as you want.
Be sure to click "Save map" after you make an adjustment to save the node positions.
You can now specify the person on your team who is focused on a particular metric. The avatar of the metric owner appears on the strategy map.
We're planning to do lots more with this in the future, like sending the metric owner automated updates on the performance of their metric.
It's now faster to make connections between nodes on your strategy map. Simply draw the connections.
You can share product updates to Slack with DoubleLoop either manually or automatically by connecting a workstream to a Slack channel.
We improved how the Slack shares look.
Minor updates
For many companies, having one strategy map isn't sufficient. For companies with many product teams, trying to model everything on one canvas gets too complex. Enabling the creation of multiple strategy maps has been our most requested feature.
Now, you can create multiple strategies in DoubleLoop so there's room for each team's strategy to breathe on its own.
To create a new strategy, click the "+" button at the top of your strategy canvas.
We're very excited about this. Now, with just a few clicks, you can add popular metrics from Google Analytics to your strategy map, like users, sesions, bounce rate, and average session duration.
After you integrate, DoubleLoop imports your past three years of Google Analytics data.
This gets powerful when combined with our other historical data importers. For example, you can pull in your full history from Jira and GitHub to see years of data of your product iterations and metrics.
You can see what happend at your company before you even worked there.
Minor updates
-
Allow the Looker Integration to parse YYYY-mm dates
improvement
-
Toggle the metrics graph to show cumulative data
improvement
-
New workstream type for "Support"
improvement
-
Share minor updates to Slack without stealing so much attention
improvement
-
Add the URL to the info tooltip for strategy nodes
improvement
You can use DoubleLoop to create a persistent model of your metrics-driven strategy. Parts of your strategy might stay the same for weeks, months, or even years.
But sometimes it's valuable to create time-based goals in the style of OKRs. Now you can add key results to your metrics in DoubleLoop!
Simply add the key result value and the target date for a metric. You can then track the status of the goal on your strategy map and drill into progress on the metric page.
Reading the name of a metric doesn't always convey what exactly is being measured. So we added a tooltip that shows the "Plain language description", "Technical definition", and "URL" of each metric. It helps you understand the metric without leaving the context of the map.
DoubleLoop rewards you handsomely for connecting your strategy map to your source tools.
Connect DoubleLoop to Slack to receive a weekly digest of how your metrics performed and the work that was done to move the metrics.
More and more companies keep signing up for DoubleLoop who use Linear. Now our Linear integration is live! You can:
(1) Add workstreams to your strategy map based on Linear projects.
(2) Automate your release note process with Linear data.
Minor updates
Previously, new users would get a blank slate after signing up for DoubleLoop. Now, we create a default map so you can see what it looks like. From there, feel free to make edits or deletions.
Previosuly, if you edited the data points for a metric, you wouldn't see it reflected on the map until the next day. Now it updates immediately.
Minor updates
-
Change the Metric page graph to be daily interval, not weekly
improvement
-
Make it easier to find API token
improvement
-
On the metrics page, sort the data points by date
improvement
-
Improve date format on the metrics page
improvement
-
When there's no metric, don't display the timeline graph on changelog page
improvement
-
When your mouse is over stratagy canvas, it should look like a grabby hand
improvement
DoubleLoop allows you to model your product strategy in the form of a flowchart. The flowchart is a map of how your work relates to the leading and lagging indicators tied to your business performance.
Now, you can see your work activity and your metric data in your strategy flowchart.
For each of your product initiatives or workstreams, you can get a quick glance into the amount of activity that's happening. You can quickly see what parts of your strategy are getting attention, or not.
For each metric, you can see how it's performing over the last 7 days, 6 weeks, or year. It gives you a sense of where your strategy is working to improve KPIs, or not working.
Altogether, our "connected
To run a metrics-driven product development process, you must have a clear thesis for how your work relates to metrics.
You can now use DoubleLoop to diagram the connections between your workstreams and the leading and lagging indicators that drive your business. Mapping your work and metrics (1) is a great way to align your team around your product strategy and (2) is the perfect entry point to using DoubleLoop.
Would you like free consulting to create a metrics-driven product development process? We’d love to help and use it as an opportunity to refine our product.
After iterating on your front-end for a while, it starts to burst at the seams. Entropy.
So we launched a new UX. It's a fresh, more spacious canvas for future iteration. Among the improvements, check out the new visual for correlating product changes with metrics changes.
Minor updates
Our blog, "The Loop," shares our thoughts and research into product building.
Our latest post, based on an interview with our new investor Dan Rubinstein, examines how the product analytics craft was practiced at Google in 2005. While the analytics that are available to product managers have exploded since Dan Rubinstein worked at Google, the principles of *how* they used those tools are poorly applied today.
The power of DoubleLoop is using our filters to separate the signal from the noise. You can filter and save views of your completed features, bugs, or epics. You can track all the work that's happening in a hot initiative. You can keep an eye on all the work that's getting close to launch.
Now, our filtering interface is much improved. You can easily discover all the ways that DoubleLoop classifies your tool activity to hone in on the work stream you care about.
When you integrate Jira with DoubleLoop, we import your full history of product changes. Now, we'll automatically generate some useful views for you of your completed features, epics, and issues. This makes keeping release notes maximally efficient. Just select which ones you want to include in your internal or public release notes and adjust the text as necessary. Launch a release notes page within minutes of signing up.
Minor updates
Imagine if you could see and share the full history of your product's evolution. Now you can! With a few clicks, we'll retroactively import all of your past product iterations from Jira, GitHub, or Shortcut.
To give it a try, request access to DoubleLoop below. When you get access to your account, after you connect your tools, you'll see release notes going back to the very beginning of your product within minutes. From there, you can immediately share it or make edits to craft the narrative.
"Learning from the past" is a basic way to achieve progress in any human endeavor. But it's almost impossible to do at tech companies where new employees are rotating through…
Now, when you share your public changelog updates in Slack or Twitter, we unfurl the images to provide eye candy for your stakeholders or customers.
A big reason to use DoubleLoop is to quickly create views of your release notes, changelogs, or initiatives that you can share with your internal stakeholders or customers.
For every "view" in DoubleLoop, the system automatically creates a stakeholder view. A stakeholder view is a read-only page that can be easily digested by stakeholders or customers. The page you're reading now is an example!
Now, you have multiple options for controlling access to these pages. Make them fully public, private behind login, or private with token access.
Minor updates
DoubleLoop creates a virtuous cycle of clarity on your team. After you connect GitHub or Jira, you can now easily read the summaries of each product change in the DoubleLoop app. Your team will be rewarded for writing useful descriptions.
Do you like how this page looks but you're not ready to share publicly? You can now create pages like this behind authentication. It's the ideal way to show your business impact to internal stakeholders at your company. Add a business KPI to your metric graph and your stakeholders will be star struck.
Just grab the URL from the settings of a view and share the link with your colleagues.
DoubleLoop pulls in the type of product change from Jira or GitHub. Or you can edit it manually.
Set your primary color in your organization settings.
Does your team use Conventional Commits? We reward you handsomely for doing so. DoubleLoop generates your changelog automatically based on data you already have in GitHub. We parse your commit messages to clean up the names and adds labels such as "Feature" or "Fix." For each week, we highlight the features and summarize all the other updates in a bulleted list below.
When you inform users of a new feature, give them a clear next step by prompting folks to "See the demo!", "Read the docs!", or "See it action!" Name the call-to-action however you want and point it to any URL.
Until today, you could use DoubleLoop to build an internal changelog for your company. Now, you can use DoubleLoop to build public changelogs to share directly with your customers, stakeholders, or investors. This page is an example!
If your team references the Jira or Clubhouse Id in pull requests or commits, it now appears as "related work" in your internal changelog. For engineers, it helps you understand the business context of code changes. For product managers, it helps you understand the effort involved with each product change.
We've invested a lot in capturing valuable info about the product change events that we import from your tools. You can now see more of this info in the Slack notifications.
Minor updates
Minor updates
Minor updates
Minor updates
Minor updates