Give merciless feedback & get Mutant 3 months for free IH

@hake, just wanted to let u know that I updated the weird-m Mutant logo :) The font I initially used was a pure mess, so I went with a safer Helvetica bet, but kept it black. Hope your eyes don't bleed anymore, at least. I'll ask a more branding-focused designer to revise it once we start to grow :)

Thank you for the feedback.

Great, it's your comment that gets up voted

I think there's another problem with the m, not the font-weight. Let me get back to you on that :)

Yes, you would use Mutant for task management (instead of JIRA) and also custom event tracking for your experiments (instead of Mixpanel).

This way the usage data will be in the context of planning/decisions.Regarding Mode, ill do some reading about it but at a glance it has a "grownup" use case where you have multiple data sources coupled with big amount of data.

We're not gonna do all that JIRA does or all that Mixpanel does, we're trying to find a sweet spot.

The main thing we want to validate is "Is this a viable way for teams to do measuring: story by story (we also have a concept of component but we'll push that further down)" and have it exposed in the air all day.

Hey Josh,

We want Mutant to provide the essentials of an issue-tracker and a usage measuring tool. So you can link real data to the success criteria of each story as easily as possible - we’re providing our own API and library for event tracking, https://github.com/mutantlove/next.

Measuring should be done like code testing, as you write code not once per quarter or siloed off to another team or delegated to the Release Manager. It should be in the fabric of daily conversations and planning.

We’re targeting Mutant at

• new tech startups (we don’t have enough to make more mature teams to switch at this point)
• tech founders that understand that the whole team needs to know how what they’re building is being used and how it moves metrics.
• PMs that give their teams a problem to solve - as opposed to describing exactly what we devs have to build this sprint.

This will not be a tool for top-down decision making or waterfall development teams that implement a task and move on.

You already have all the building blocks, you have a issue-tracker and you have an analytics tool. With a plugin (GA -> JIRA lets say) and manual work from the PO, success metrics for a story can be achieved and published. The current state of achieving this is slow and ineffective, so almost nobody does it. Except the really big companies, that ALL do it with internal tooling.

We want to make it trivial simple, just like in the gif: you have a story and you plot what event makes sense in that context, dynamically and in real time.

Hope this helps.

James, thank you so much for your feedback!

• Yes, we're asking users to switch to an initial crappy product :) we know how difficult it is to setup an issue tracker - and hope to provide so much more value that you actually do that.
• Thank you, we also think it's useful to see the state of analytics before and after a ticket is released. We also want to make it possible for you to see which tickets impacted a certain metric.
• I get it, totally. But we decided not to build on borrowed land. We'll see how that goes...

Very helpful, thank you. If you decide to make the switch, or for a younger product, maybe, please give us a try.

Hey Bruce,

Thanks for the the feedback and questions.

1. Analytics API: we provide our own. Right now we can only collect browser events through https://github.com/mutantlove/next. More to follow depending on our first users - NodeJS, Php etc.

We decided that have control of all aspects (analytics and issue tracking) and not be another integration tool. It's better for what we want to build.
We want to cleanup and simplify as much as possible this planning <-> measuring cycle and using other tools would not give us the freedom that we need. I know this brings the topic of switching ): but I think we'll provide enough value to switch from 2 tools to Mutant in long run.

2. Privacy: At this moment we're just counting how many times did event with name X occur per day (we do hold the individual event, not just the aggregate). We are saving the IP, referer, user agent, screen size and time stamp. We also allow users to attach custom data to each event. At some point we'll add the possibility to plot that custom data (as I'm writing this I realize that this info should also be in the GitHub repo).

There is a balance here that we'll need to keep, flexibility vs anonymization. We're also considering end-to-end encryption but at this validation and mvp stage we're going for the path of least resistance.

Privacy is an important topic for us and personally I would love at some point to stop sending my data to Google or Ads Inc. and know that certain corners of the internet are private, including my company's analytics data, even if I have to pay a bit more.

This is not to say that we've ruled out the full aggregate approach of Fathom Analytics. It's something we'll have get a bit more data and feedback on.

3. Mobile: Yes, we know, sorry for that. As I said we're in mvp'ish stage and pushing hard to validate the idea. We're gonna postpone it a few more days, if mobile vs desktop is comparable we'll spend some time and fix it since it's creating more friction for users than saving us time.

Hope this helps, if not, tell me more :). Let me know if you decide to give it a try and I'll send you an invite.

Best and thanks again

Hi aoveri,

I also spent some years doing this product thing you mention. And we noticed how difficult was to really bring data into discussion and make everyone in the team feel compelled to move that metric. Mostly because the metrics visible to everybody felt kind of generic - somewhere on the wall there was a dashboard - and everybody actually delivered features that somebody else decided, without actually understanding how their work affects the users.

So we wanted to create a very simple way to bring everybody on the same page and really dig into the kind of data that creates product intuition - for designers, developers, UX writers, PMs. And the best way to do this is to attach relevant metrics to each user stories - for now we added only analytics, but we want to add qualitative metrics (user feedback), too.

I think an issue tracker should be smarter then a wall full of post-its. And, because none of the ones you mentioned were (they all do, basically, post-it management at scale), we started building one. To replace them all :)

Please let me know if you want to give Mutant a spin.

Hi Luqa, thank you for taking the time to check it out. We did 0 optimization for mobile screens, I apologize for that experience. We had to prioritize other things at this point, as our main audience is on desktop.

Thank you for your feedback on the copy, we'll definitely look into that. We try to explain the concept in the simplest way we can think of, so visitors actually understand what we do differently then other issue trackers. Did we manage to transmit that for you?

I am really sorry you didn't like the modified m's. I personally love them! I'll wait for a little bit more negative feedback on that to change my mind :)

Please let me know if you would like to try Mutant for managing the work on your product.

Got it. "After you've worked on a site for even a few weeks, you can't see it freshly anymore. You know too much. The only way to find out if it really works is to test it." - the same Steve Krug.

Thanks for your feedback.

Hi @Primer we removed the cheesy joke from the hero copy in Mutant's homepage. You were absolutely right.

Thanks for the great feedback.

https://i.pinimg.com/736x/20/08/d3/2008d3e1014e8220bd2b786f9373ba02.jpg

From a different bible