WhatsApp Events 📱

TASK:

Whatsapp groups should have the ability to make plans with the people in the group.

Plans would be simple single task activities (like dinner, concerts, etc.). Not things like trips to other places/countries (which would have a lot of sub-plans within the plan)

Expected Task Output:

You have to scope out how such a feature would be implemented. Your thought process should come across clearly. You should also have a couple of wireframes for the same to illustrate how you would get a designer to start designing for your feature. Pen and paperwork so do any other tool that you feel like using. You should also break down your thought process and point out what kind of considerations you made while coming up with this feature.

My Approach:

1. Understand the Task Better — Q&A.
2. Overview on Instant messaging Market & Whatsapp Product (Market & User Research).
3. User Needs/ User Pain points.
4. 6 step solution — Brainstorm, Prioritise, Test, Implement, Analyse, Systemise.

• MVF, User Flow, Sketch, Wireframes, Mockups, Success Metrics, Go — To — Market Strategy, Roadmap.

UNDERSTANDING THE TASK BETTER:

1) Q&A:

1. What is the real goal of building a feature like “Make Plans in the Group” for WhatsApp? Just curious to know whether this feature is being built & launched due to intense requests by the users or any business objectives like to improve Engagement, CSat, or any other goals? Ans: User requests, not sure how this feature will impact engagement — you can explore this in the scope out.
2. Since WhatsApp is adopted by a large number of people across the world. Whom are we targeting this feature with? any specific Personas, Demographics, etc., or Can I assume this on my own? Ans: Let’s scope out keeping at least 3 demographics in mind.
3. Any Metrics, Time Frames, Budgets, Resources, or Dependencies that I need to keep in my mind? Ans: This will be an MVP so we will try to reuse as much code as possible.

2) Assumptions:

1. I am considering the whole assignment on the Peer — Peer side and not on the business side, meaning Businesses that own Whatsapp groups for Customers in engaging them with Updates, Newsletter, Support, etc.,
2. Since Whatsapp is available on different platforms (Web, Android, Apple, etc.,) I am assuming to first design for Android due to its Majority of Users coming from Android share.

Ans: Both assumptions look good to me.

I have taken a Lean Product approach in order to solve this Task. I would first go in-depth with Problem space and then talk about Solution Space. Hence I am dividing this assignment into two parts. They are:

• Problem Space: wherein would like to break the Problem in-depth in order to understand the right Problem which needs to be Solved. The Problem space includes identifying the right Target Customers, understanding their Underserved needs, and coming up with the Value Proposition for the same.
• Solution Space: Try and address the identified problem to achieve the desired goal. The Solution Space includes building the Right Feature Set and UX.

The below image is for the reference of the Lean Product Process by Dan Olsen.

OVERVIEW:

Instant Messaging has grown noticeably in India since Internet was made cheaply accessible. Either it’s keeping in touch with Friends and Family, talking with Close Pals and planning things (Big and Small) that happen here. One such Instant messaging application which is heard all over the World is Whatsapp.

WhatsApp is an American freeware, cross-platform messaging, and Voice over IP service owned by Facebook, Inc. It allows users to send text messages and voice messages, makes voice and video calls, and share images, documents, user locations, and other media.

WhatsApp was launched on 3rd May 2009. As of February 2020, WhatsApp had over 2B active worldwide users.

In the last couple of years, WhatsApp usage in India has boomed. Very likely that someone in the family — parents, relatives, grandparents, etc. use WhatsApp a lot.

• They use it to keep in touch with family, relatives, close friends, an extended network of friends, people in the neighborhood, businesses, etc.
• They use it for different purposes: Entertainment, communication, information, buying and selling, discovery, maintaining relationships, etc.
• This is a fairly new development, and it wasn’t the case 5 years ago. Some of them might be using it a lot more than you do!

Why WhatsApp has fit into every Indian’s life so easily❓

After 11 years of its initial launch, the product has hooked itself into the daily life of every user in such a manner it feels nearly impossible to believe a world without WhatsApp. I conducted some research to find out why it fits so well in peoples’ lives and is at par with its competitors in the Indian market.

• First in the market: WhatsApp was the first text-based messaging platform that was launched. Being the first, it became popular among people in a very short span of time.
• Timing of launch: WhatsApp was launched in 2009, approximately the same time when smartphones were launched in India. It gave people a chance to try the new tool on a newly launched device.
• No ads, games, gimmicks: There are no in-app ads or games, making the interaction with the app smooth and less frustrating.
• Low-cost usage: The cost of using WhatsApp is very less. The app is free, and there are nominal charges while using mobile data.
• Works on various platforms: WhatsApp is supported on almost all mobile platforms and also on certain PC platforms as well.
• No need to add contacts: WhatsApp automatically imports data from contacts to show the WhatsApp account of the person.
• No international charge: There are no international roaming charges when communicating with people across the globe.
• Easier handling of groups: WhatsApp groups are easier to handle with added personalization, unlike the FB groups.
• Monitoring online stalking: Hiding of ‘online,’ ‘last seen,’ etc., to prevent people from online stalking your profile.
• Status Update: Allows people to get creative with the status and easily change and come up with new status. from time to time.
• Expanded features: Features such as group video call, WhatsApp story, sharing location, etc. gives users more room to share and lead a meaningful social life.

And the popularity emerged due to its frictionless multiple features like Chatting, Audio & Video Call, Ability to share Pictures & Videos, send Recorded Audio notes seamlessly and also many other features like:

https://uxplanet.org/genx-and-whatsapp-a-ux-research-case-study-5d7f746b9ae8

BUT THE PROBLEM:

Narrowing down the Problem Statement to Whatsapp Groups Feature as the above-mentioned Task expects to do the same.

Most plans however on Whatsapp Groups, fail because someone did not respond in a group, because they could not find more information about the plan or did not know who all are going. It is important and motivating to see how many people are going to be able to refuse with awkwardness. The existing solutions for group chats do not address these needs. Even planning is a nightmare.

MARKET RESEARCH:

Interestingly, Facebook Messenger’s AI ‘M’ already suggests features to use based on your conversations. Read the complete article here.

https://techcrunch.com/2017/04/06/facebook-messengers-ai-m-suggests-features-to-use-based-on-your-convos/

On similar lines, iOS create smart links whenever a day or time is mentioned, it is underlined, and links to schedule in your calendar. Find the screenshots below.

USER RESEARCH:

1) Target Users:

Since WhatsApp has multi-million users it has a substantial reach. There are users in every segment of the digital platform. I considered creating 3 user personas that included demographics, goals, and behaviors which I can use to build my feature. This helped me start to envision the kind of problems that such a user would have.

Ideally, target users are young people between the ages of 20–40. Older people are more likely to be comfortable with communicating via the phone than via text messaging since it’s not typically a generation that is looking at the phone all the time.

Source: Livemint

This proto-persona was based on a lot of assumptions that required further research for validation, but it was a quick way to guide myself through the Task. To save time, I didn’t create a fancy layout.

Ps: You can view all my original design files **here on Figma**

Based on my Research and User Interviews, here is the list of most probable events planning that happens over Whatsapp Group for personas between 20–40 would be:

• Travel Plan
• Dine Out
• Movie or an Event Plan
• Shopping
• Community Meet-Up
• Get Together etc.,

And the most probable way of doing it would be by creating a separate WhatsApp group, texting individually, and here are a few of the pain points experienced every time while making a plan:

• Users don’t get a confirmation for the guest's approval.
• Users have to do a lot of tasks to reschedule an event.
• Users cannot plans without friction or spending more time to do it, by chatting, discussing, verbal calls, and more.

2) User Needs:

I am Categorising users into three sections for this feature, based on the type of Actions, and then list down all the user needs accordingly. They are:

• Event Host
• Event Attendee
• Group Admin

Event Host:

• As a Host, I would like to create a new event, so that I can plan events in the group easily.
• As a Host, I would like to add details about the event like Event picture, Details (Date, Time, Location), Category, Respond Timer, Expiry Timer, Notes, Co-Host**,**, etc., for the event, so that it helps attendees decide both quickly & accurately.
• As a Host, I would like to define a number of Slots in the event, so that group members can join in. (First Come — First Serve Basis).
• As a Host, I would like to add a Co-Host for the Event, so that the other person can help organize the event more efficiently in Larger Groups.
• As a Host, I would like to edit all the details, so that I can edit event details again and send the update.
• As a Host, I would like to accept responses (interests) so that attendees can notify me about their interests.
• As a Host, I would like to see and reply back to Queries, so that attendees can stay updated about the doubts they have.
• As a Host, I should be able to request attendees again, so that attendees can change their responses even at the later stages.
• As a Host, I would like to keep track of all the Hosted, Cancelled, Pinned & Archived events across various groups, so that I can be prepared.
• As a Host, I would like to Re-host the most loved Event again by a single Tap, so we can plan more and more events often and easily.
• As a Host, I would like to sync Whatsapp events with my Google Calendar, so that I will never lose track of events.
• As a Host, I would like to pre-schedule the Event in advance, so that I can prepare the events to list well before posting it in the Groups.
• As a Host, I would like to invite specific members inside a group for events, so that I can premium a few members.
• As a Host, I would like to delete the event by Notifying all the Members of the Event list, if we had any change of plans in the End.
• As a Host, I would like to receive feedback from the attendee’s post Event, so that the Host can improve the overall experience of the Event.
• As a Host, I would like to host “Pay & Join Events”, so that attendees can join events only by paying.
• As a Host, I would like to get recommendations about the events and options to book/pay, based on the type of event created. Eg: The event: Coffee Meet-up, Recommend Place: WhatsApp suggests coffee shops. Service: Book Table and Pay.
• Events should trigger on their own when someone mentions keywords like catchup, around, time, meet up, movie, shopping, etc.,
• As a Host, I would like to have an option to Report Event, so that it helps to keep Events clean and Simple.

Event Attendee:

• As an Attendee, I would like to notice the event easily, which is probably lost in random conversation.
• As an Attendee, I would like to see details about the event like Event picture, Details (Date, Time, Location), Category, Respond Timer, Expiry Timer, Notes, Co-Host, Number of Slots, etc., for the event so that it helps me to decide quickly and accurately.
• As an Attendee, I would like to reply to the invitation, so that I can confirm the Host.
• As an Attendee, I would like to write a Query about the Event, so that I can write directly to the Host and get clarity before the Event.
• As an Attendee, I would like to keep track of all the Hosted, Cancelled, Pinned & Archived events across various groups so that I can be prepared.
• As an Attendee, I would like to propose a new date or time (feedback pre-event) if possible.
• As an Attendee, I would like to sync Whatsapp events with my Google Calendar, so that I will never lose the track of events.
• As an Attendee, I would like to share the expense of my event at the same place, so that I don’t have to discuss and do it using multiple applications.
• As an Attendee, I would like to give feedback to the Event Admin post-event, so that the Host can improve the overall experience.
• As an Attendee, I would like to have an option to Report Event, so that it helps to keep Events clean and Simple.
• As an Attendee, I would like to exit event, so that I can exit when i feel not interested.

Group Admin:

• As an Admin, I would like to set access, so that only they can create Events in the Group.
• As an Admin, I would like to turn ON & OFF for automatic Event triggers based on the Chats (based on keywords like catchup, around, time, meet up, movie, shopping, etc.,)

Once we know the Problem Space well ie., Overview, Market, and Users — their needs and paint point. It’s time for us to look ahead and drive the Solution.

I am deriving solution using 6 Steps: They are:

1. Brainstorm
2. Prioritize
3. Test
4. Implement
5. Analyze
6. Systemize

STEP ONE:

Step 1: Brainstorm in other words means, Generate a lot of ideas using Market Research & User Research. This can come from anywhere, maybe from the organization or from the customers or from someone who never used the product.

Usually, before starting, the task is shared with everyone to ideally come up with the ideas. Now, Let’s start by listing all the recommended feature attributes at each stage which we did in Problem Space.

STEP TWO:

Step 2 — Prioritise in other words mean, Organise and Prioritise multiple functionalities for a Feature. Rate and Compare their potential impact, confidence and resources required. It’s very important to acknowledge the fact that not every attribute/functionality can be implemented considering Time, Effort, Cost, and Resources. So I am Prioritising attributes / Functionalities accordingly.

The kano framework is another excellent framework for understanding customer needs and satisfaction. The utility of the model is that it breaks customer needs into three relevant categories that we can use for our case study. They are Must Have’s, Performance Benefits, and the Delighters.

Kano Framework for Feature Prioritisation

Applying Kano Model to Event planning feature. I would be to divide all the User Needs/Functionalities into Must Have’s, Performance Benefits, and the Delighters. Here are they:

A) For Event Host:

Must Have’s:

• As a Host, I would like to create new event, so that I can plan events in the group easily.
• As a Host, I would like to add details about the event like Event picture, Details (Date, Time, Location), Category, Respond Timer, Expiry Timer, Notes, Co-Host, etc., for the event, so that it helps attendees decide both quickly & accurately.
• As a Host, I would like to edit all the details, so that I can edit event details again and send the update.
• As a Host, I would like to accept responses (interests) so that attendees can notify me about their interests.
• As a Host, I would like to keep track of all the Hosted, Cancelled, Pinned & Archived events across various groups, so that I can be prepared.
• As a Host, I would like to delete the event by Notifying all the Members of the Event list, if we had any change of plans in the End.
• As a Host, I would like to have an option to Report Event, so that it helps to keep Events clean and Simple.

Performance Benefits:

• As a Host, I would like to add a Co-Host for the Event, so that the other person can help organize the event more efficiently in Larger Groups.
• As a Host, I would like to define a number of Slots in the event, so that group members can join in. (First Come — First Serve Basis).
• As a Host, I would like to see and reply back to Queries, so that attendees can stay updated about the doubts they have.
• As a Host, I should be able to request attendees again, so that attendees can change their responses even at the later stages.
• As a Host, I would like to pre-schedule the Event in advance, so that I can prepare the events to list well before posting them in the Groups.
• As a Host, I would like to invite specific members inside a group for events, so that I can premium few members
• As a Host, I would like to Re-host the most loved Event again by a single Tap, so we can plan more and more events often and easily.
• Events should trigger on their own when someone mentions keywords like catchup, around, time, meet up, movie, shopping, etc.,
• As a Host, I would like to receive feedback from the attendee’s post Event, so that the Host can improve the overall experience of the Event.

Delighter:

• As a Host, I would like to sync Whatsapp events with my Google Calendar, so that I will never lose the track of events.
• As a Host, I would like to get recommendations about the events and options to book/pay, based on the type of event created. Eg: The event: Coffee Meetup, Recommend Place: WhatsApp suggests coffee shops. Service: Book Table and Pay.
• As a Host, I would like to host “Pay & Join Events”, so that attendees can join events only by paying.

B) For Event Attendee:

Must Have’s:

• As an Attendee, I would like to notice the event easily, which is probably lost in random conversation.
• As an Attendee, I would like to see details about the event like Event picture, Details (Date, Time, Location), Category, Respond Timer, Expiry Timer, Notes, Co-Host, Number of Slots, etc., for the event so that it helps me to decide quickly and accurately.
• As an Attendee, I would like to reply to the invitation, so that I can confirm the Host.
• As an Attendee, I would like to keep track of all the Hosted, Cancelled, Pinned & Archived events across various groups so that I can be prepared.
• As an Attendee, I would like to have an option to Report Event, so that it helps to keep Events clean and Simple.
• As an Attendee, I would like to exit event, so that I can exit when i feel not interested.

Performance Benefits:

• As an Attendee, I would like to write a Query about the Event, so that I can write directly to the Host and get clarity before the Event.
• As an Attendee, I would like to propose a new date or time (feedback pre-event) if possible.
• As an Attendee, I would like to give feedback to the Event Admin post-event, so that the Host can improve the overall experience.

Delighter:

• As an Attendee, I would like to sync Whatsapp events with my Google Calendar, so that I will never lose track of events.
• As an attendee, I would like to share the expense of my event at the same place, so that I don’t have to discuss and do it using multiple applications.

C) For Group Admin:

Must Have’s:

• As an Admin, I would like to set access, so that only they can create Events in the Group.

Performance Benefits:

• As an Admin, I would like to turn ON & OFF for automatic Event triggers based on the Chats (based on keywords like catchup, around, time, meet up, movie, shopping etc.,)

1. MVP of Event feature:

At first, we have decided to launch an MVF (Minimum Viable Feature). So lets start with the process:

MVF by Dan Olsen

The above picture illustrates the difference between the Correct and Incorrect ways of representing the Minimum Viable Feature. A pyramid of four hierarchical layers is used to describe a product’s attribute. They are:

• Functional.
• Reliable.
• Usable.
• Delightful.

whereas the pyramid on the left illustrates the misconception that an MVF is just a product-limited Functionality, and the Reliability, Usability, and Delight can be ignored. Instead, the pyramid on the right shows that while an MVF has limited Functionality, it should be “complete” by addressing those three higher-level attributes.

Functionalities Scoping for MVF:

Since we do not have a cap on any resources, timelines, Budgets, or Dependencies. I will put users first approach to carve out attributes/functionalities for this Feature.

I am considering all “Must Have’s” from Host, Attendees, and Admin since they are the least/must-have attributes without which a user would not use the Feature.

For Performance Benefits. I listed and rated the users’ desired outcomes by how important they were and how well satisfied they were with current solutions. This enabled me to prioritize and pinpoint exactly how my solution would solve the user’s problems better than the current solution.

I assumed that the user would be using an existing solution on their phone, and rated how these outcomes would be satisfied by the alarm, and Calculated the Total score using the simple Formula.

Importance — Current Satisfaction = Opportunity

Based on all the above Prioritisation, Here is the list of final functionalities for MVF (version 1 — Includes Must Have’s and Performance Benefits):

Final MVP Functionalities for Host, Attendees, and Admin:

Some desired outcomes had a low opportunity score while having a high importance score. These outcomes are already satisfied. I categorized these as baseline outcomes, meaning that users expect all solutions to achieve these basic results.

At this point, I was able to see opportunities for current solutions as well as basic results I needed to provide for the users.

*Note that so far the desired outcomes, the importance, and how well they’re satisfied are all assumptions. For a real-world project, in-depth user interviews are required to validate these assumptions.

STEP THREE:

Step 3: Test means Executing all the prioritized ideas in smaller steps. We do Smoke tests and collect Qualitative & Quantitative data around it using WireFrames etc. It’s mostly open for targeted personas and a small chunk of the audience ie., Sample Size, and named Minimal Viable Test. It saves a lot of Effort, Time, Cost, and Talent. In order to do that, We got to Develop our Wireframes first.

1. User flow:

Here’s the key user flow, I have created based on the storyboards.

User Flow Diagram

Ps: You can view all my original design files **here on Figma**

2. Sketches:

The user flow I created in the previous step made sketching the screens a lot easier because I was clear about the main actions the user needs to take on each screen.

My goal with the sketches was to quickly jot down my thoughts knowing that I’ll probably make some more changes when I create more detailed wireframes.

3. Wireframes:

Ps: You can view all my original design files **here on Figma**

STEP FOUR:

Step 4: Implement meaning Creating High-Level Mockups using User Flows, Sketches, and Wireframes and then rolling it out as an MVF for our Targeted Audience. This is the first step taken to show the MVF with the real users and understand/record their interactions. Post which, We could analyze and Improvise.

1. Mockups:

My step 1 was to create a Design system after Wireframes, post which I created a detailed set of Mockups to represent Individual Screens.

I chose a shade of Green which is already associated with the Whatsapp Application. The shade of white just blends with Green in the Light Theme.

Ps: You can view all my original design files **here on Figma**

2. Go-To-Market:

A Go-To-Market Strategy is a comprehensive action plan to successfully launch a product/Features in the market. Building an effective Go-to-Market strategy is an important aspect of the entire product development because It largely determined the success of a product or service when it is launched in the market.

The basic advantages of having a well defined go-to-market strategy are as follows:

• Helps companies to understand their target market and target audience better
• Enable effective utilization of Time and Resources
• Helps companies to minimize their overall cost

A go-to -Market plan is needed at many stages. A few of them are:

• A company is looking to launch a new product in the market.
• A company is looking to launch an existing product in the new Market.
• A company is looking to launch a new feature of an existing product in the Market.

Go-to-Market Strategy itself includes many parts in itself. They are:

• Understanding the product and the market.
• Product Launch plan.

Here is the Go-to-market Strategy for Whatsapp Feature. Let's take it step by step:

Understanding the product and the market:

I have already defined what Ideal Users would look like for this Feature- their persona, their pain points, and the competitors around by pinpointing their Strengths and Weaknesses. It’s time for us to think about a strategy to ensure that your product achieves a long-term Product Feature fit.

Achieving Long Term Product Feature Fit is a constant and iterative process. Constantly revisiting our understanding of the market, our product offering, and its value proposition, and the messaging is critical to ensure constant Product Feature Fit where the market and customer’s needs are also constantly changing.

Initial user feedback can be gathered using some of the techniques mentioned below:

• Beta launch: Feedback from early adopters of the product / Features.
• User voice: Forums where existing customers can provide feedback for the product teams.
• Customer interviews: Product teams directly engaging with ideal target customer personas to get feedback.
• Market research: Through independent forms, analysts and industry surveys.
• A/B testing: On the website, to see how different visitors interact with the product/platform.

Beyond the initial product-feature fit, the company can continue to use the following to gather ongoing customer feedback. This feedback should be effectively routed to the appropriate teams (Product, Marketing, Sales, Support) such that changes are made to ensure fit for the long term. There is also a need for ongoing research to understand market trends so that the product can be tweaked accordingly. In some cases, when a company introduces new products/features, it could potentially change/ expand the customer profile.

Product / Feature Launch plan:

The Product Launch plan is divided into 3 major parts. They are:

• Pre Launch Phase
• Launch Day
• Post Launch Phase

1. Pre-Launch Phase

• Identify a date of launch giving sufficient time for planning and product/launch readiness. This will require working with different teams, including product, engineering, sales, marketing, and support.
• Identify a handful of beta users, and gather initial data on the efficiency of using Track in their businesses, and assess how the usage of Track compares to some of the other collaboration tools that they may have used previously.
• Refine the product messaging to reflect the focus on solving customer needs and adding business value.
• Define a two-minute product pitch that can be used by teams across the company.
• Conduct internal training sessions to ensure consistency in product messaging across various teams.
• Having an FAQ document with product details is also very helpful.
• Define KPIs to be tracked on the launch day for Track. These could be: a) Engagement, b) Retention, c) Usage Patterns, d) recurring users, session intervals, session length, time spent on the app
• Building dashboards to track these KPIs would be the next step. It is important to ensure that the product feature and their functionalities work for the audience that we are targeting;
• Ready social media channels for the launch with the right messaging and gather initial traction and followers for the channels.

2. Launch Day

• Publish a blog on the website and social channels announcing the launch of the product. This blog will also include quotes from users who participated in the beta test.
• Have popular media channels (e.g., TechCrunch) cover the product launch and key features.
• Run gamified audience engagement through early access, freebies, etc. on launch day.
• Do live tracking of KPIs.
• Effectively map out the customer journey and identify areas of friction during usage that cause users to drop off; this could be at the sign-up stage, the email confirmation stage, or the payment stage.
• Reach out to customers who signed up, to understand their experience and gather feedback on areas of improvement. Repeat this for customers who did not sign up, to understand their reasons. This will help go back and make adjustments to the sign-up workflow.

3. Post-Launch Phase:

• Check all data, including:
• Rates of acquisition, adoption, conversion, the efficiency of the various sales and marketing channels for Track;
• Run analysis on the users signing up for the product to confirm that it matches the customer segment identified to make any changes if there is a mismatch;
• Any areas of customer feedback that needs fixing, based on proof such as customer stories and testimonials from the initial adopters on the user experience and benefits of Track to their business.
• Enhance ongoing customer support and long-term customer journey.

STEP FIVE:

Step 5: Analyse meaning Compare results to your hypothesis and ask why. Below is the list of Success which we would collect data for and Analyse their results at regular intervals of time. This helps to conclude things down, whether to Preserve or Pivot Feature attributes.

1. Success Metrics:

For a feature to be successful, user engagement is the key goal. To measure the success, the purpose of the feature, outcomes, and goals should be clear to determine the right metrics for the feature. Below I’ve tried to list down few steps we can take to measure that.

Step 1: Measure basic usage of the new feature: Track the number of users on a daily, weekly that can be further broken down by device, age, demography, and others. This helps in planning for the growth of the app as well.

Step 2: Users: The active user metrics are different than app installation, where you can even track the recurring users, session intervals, session length, time spent on the app to capture the feature usage patterns.

Step 3: Usage Patterns: Start analyzing the type of events users are creating and sharing. What is the response for the events shared by and from the users which you can monitor to build better retention.

Step 4: Retention: Retention is critical to the success of any app. The retention rate of the feature in the last 30 days to understand the addiction of the users to the feature introduced. Real-time tracking or cohort tracking highlights the most valuable and engaged users list to create a more robust UX to build a better app experience.

Step 5: Measure the impact of the new feature on engagement: You can start by monitoring the users who are creating events, these users are more active than others. This percentage can help you in making decisions to build better engagement.

Final step: Test, measure, repeat

STEP SIX:

Step 6: Systemise which means once the test is completed, go back to plan and write the summary of everything that happened in a loop. If the Test fails, understand why, and if the test wins Go ahead and execute it in full fledge to take it to a larger part of the Audience.

This drafted Report is always can use again as a Playbook before starting a different test again for learnings.

EXPECTED RESULTS:

However, I think the largest victory for me was to work on an intuitive approach to plan events. The focus should always be on the experience, which in this case was the user being able to plan events to create an experience for the group. And of course, the best UI is invisible.

The response expected is overwhelmingly positive, from users. Users generally find it difficult to plan events across in a group because of the infinite chatting process and not concluding on anything until properly communicated but the Events Feature will solve it all.

What to expect in the future? (Roadmap):

Roadmap for Dev

Ps: You can view all my original design files **here on Figma**

Did you know 😲

You can give up to 50 Claps for an article? Click/Tap and hold the clap button for a few seconds and BAM! Try it out 😋

Thank you for reading, hope it helps ✨

Follow me on Linkedin|Medium|My Portfolio

References:

Topic: WhatsApp

Company WhatsApp | Cleverism.com

Ps: You can view all my original design files **here on Figma**