event

give me 2 impact statements of how to summary what can be done using online controlled experiment in Mixpanel kapa.ai

How does Mixpanel achieve its randomisation and how does it select the unit/metric to use Give me 2 impact statements to include in a CV for an insurance platform where we are driving the uptake by creating a beta homepage, driving traction to use retirement quotes, processed applications, transfer in/transfer out applications add numbers to it kapa.ai

You don't get it but what is your responsibility and the responsibility of the CMS system like acoustic meant to manage when you're using a co-dependent system kapa.ai

How do we determine the parameter, randomisation unit to use, we are using users but how are the split selected, we make use of a codeless CMS to determine the profile/group that sees what screen I think we can use that to determine but what randomiser is used and how is this achieved, is it in the code implmentation? using wording flags? kapa.ai

How to build a pie chart in power bi kapa.ai

Describe the problem (or opportunity) you’re trying to solve. Why is it important to our users and our business? What insights are you operating on? And if relevant, what problems are you not intending to solve? kapa.ai Answer using this question framework above

kapa.ai give me this structure Problem Alignment The Problem Describe the problem (or opportunity) you’re trying to solve. Why is it important to our users and our business? What insights are you operating on? And if relevant, what problems are you not intending to solve? High-level Approach Describe briefly the approach you’re taking to solve this problem. This should be enough for the reader to imagine possible solution directions and get a very rough sense of the scope of this project. (e.g., if “The Problem” was engagement in the design process from non-designers, “The Approach” might be a feed which surfaces work that's relevant to them.) Goals & Success What does success look like? What metrics are you intending to move? Explain why these metrics are important if not obvious. Solution Alignment Key Features Give an overview of what we’re building. Provide an organized list of features, with priorities if relevant. Discuss what you’re not building (or saving for a future release) if relevant. Key Flows Show some mocks/embeds of the experience. Link to any other documentation as necessary. In general, it’s helpful to organize these around certain user journeys / use cases. Show enough of a clickthrough where people can walk away with a reasonable understanding of how the product works. Embed example: https://www.figma.com/file/Buoh8VFfzj1Qil6heQWU0h/Twigma-Checkout-Flow?node-id=0%3A1

⭐️ Now you can embed private Figma files, too!

Open Issues & Key Decisions Keep track of open issues / key decisions here. Sometimes, certain decisions are made that might feel controversial; document these here so people know that the discussions have happened and there’s strong awareness of the tradeoffs. Launch Readiness Key Milestones Identify any relevant milestones (e.g., a Dogfood or Beta milestone) that people should know about. Make sure to show when you’re expecting to publicly launch, too. DateMilestoneAudienceDescriptionMon, May 4Dogfood 🐶Internal employees onlyTesting internallyMon, May 11Beta 👥Early cohort of 100 customersGetting user feedbackTue, May 19Launch! 🚀Gradual ramp over the day to 100% of all usersIt's the big day! Launch Checklist Make sure you answer all of the questions below and involve necessary stakeholders. AreaQuestionAnswerInstructions if "Yes” (or unsure)SupportWill new learning material be needed (or updates to existing documentation)? Help Center articles? Images/GIFs? YouTube videos? Plugin documentation?YesTalk to the Product Education team.SupportWill this feature require new support processes, like saved replies, new tags to track feature changes, or training the support team on new products/changes?NoTalk to the Support team.Growth & DataHave you implemented sufficient tracking in order to measure success, risks and impact on user behavior for the new feature?Involve your data counterpart to make sure feature is well instrumented.Growth & DataCould this impact Growth numbers? (E.g., impact to NUX, UI changes to CTAs.)Let the Growth team know. Consider running this as an A/B if you haven’t already.Growth & DataAre we turning this feature on for everyone immediately (versus a gradual rollout)Defend in this section why you’re opting for an instant ramp to 100%.MarketingAre we running a Beta for this?Talk to the PMM team.MarketingDo we need an onboarding experience?Talk to the PMM team.EnterpriseWill this be available only in certain tiers (Pro or Org)?Make sure the Enterprise team is in the loop and have good reasoning for your packaging decisions. In addition, if this is to be included in sales enablement material, talk to your PMM.EnterpriseIs this a new action that should be included in the Activity Logs? Talk to the Enterprise team.PlatformAre you introducing new functionality that we’d want to add to our Web or Plugin APIs?The general expectation is that the feature team builds these capabilities into these APIs. Talk to the Platform team if you have questions.PlatformCould this break any existing integrations (e.g., with Zeplin, JIRA)?Talk to the Platform team.PlatformWill this introduce new work on mobile or mobile web?Talk to the Prototyping team.Security & PrivacyAre you introducing new data models, or exposing new API end points? Or are you changing anything to do with Authentication, Sign in, or Sign up? Is data flowing to a new vendor or outside of Figma prod ?Talk with the Security team.Security & PrivacyAre we collecting any data that we did not already, or are we using any data in a manner that we did not already use it in?Talk with the Legal team.