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.
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.
Now you can see a big picture view of your product initiatives and subscribe to ones you want to stay up-to-speed with.
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.
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.
Sometimes a feature or fix is worth mentioning to your customers, but it doesn't require a prominent treatment. Now, you can share a list of "Minor updates" for each week in your changelog.
Make your changelog feel like part of your brand. Just go into organization settings and upload a logo.
DoubleLoop now sends automated digest emails. It's a great way to stay on top of launch activity at your company or share updates with your customers.
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.
Thanks to our new Zapier integration, you can now add events to your internal changelog when you, for example, send a newsletter via Hubspot or Tweet. Coupled with our Google analytics integration, it's a powerful way to show the impact of your marketing initiatives.
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.
Our metrics graph just way more useful.
We opened up our new integration-centric product to a limited group for feedback.
We filter out the noise from bot code merges (like dependabot) so you can focus on the product changes that matter.
Build a timeline of your product with GitHub data.