Driving Academy

AMG Driving Academy

Problem Statement

AMG Driving academy, a car racing event organizer is planning to build a new platform to host their upcoming car racing event. The platform aims to provide a comprehensive solution for the participants, spectators, and event organizers to engage with each other before, during, and after the event.

Case Study Task: The solution should cater to three user groups: participants, spectators, and event organizers. The application should have the following key features:

• Participant registration

• Race schedule and location information

• Live streaming of the race

• Interactive map of the race track

• Race results and statistics

• Social media integration

• Feedback and rating system Your task is to design the experience for the above user types.

Deliverables: A presentation deck that includes IA, wireframes, mockups, design considerations and Visuals.

User Research

After doing a deep research I came to know below pain points of users from different age group.

Complexity of Form:

Pain Point: A complex and lengthy form may discourage organizers from initiating the event creation process.

Consideration: Design a user-friendly interface with a clear and intuitive flow. Break the form into manageable sections and provide guidance along the way.

Lack of Clarity on Requirements:

Pain Point: Ambiguity or lack of clarity about the required information for the event might lead to incomplete submissions.

Consideration: Clearly communicate the necessary details and provide tooltips or information icons to explain each field.

Limited Customization Options:

Pain Point: Organizers may find the form restrictive if it doesn't allow for customization based on the unique aspects of their event.

Consideration: Provide customizable fields or a section where organizers can add specific details about their event.

Technical Glitches:

Pain Point: Technical issues, such as form submission errors or slow loading times, can frustrate organizers.

Consideration: Conduct thorough testing to ensure the form functions smoothly. Implement error handling and provide clear error messages.

Inefficient Data Management:

Pain Point: Difficulty in managing participant data and event details efficiently after submissions.

Consideration: Include features for easy data export, participant management, and integration with event management tools.

Communication Challenges:

Pain Point: Lack of communication channels or updates regarding the status of the submitted event.

Consideration: Implement an automated email confirmation system and provide a dashboard where organizers can track the status of their event submission.

Unclear Terms and Conditions:

Pain Point: Ambiguity in the terms and conditions may lead to misunderstandings or disputes.

Consideration: Clearly articulate terms and conditions, ensuring they are easily accessible and understandable. Include a checkbox for organizers to confirm their agreement.

Limited Marketing Support:

Pain Point: Lack of tools or guidance for organizers to effectively market and promote their events.

Consideration: Offer marketing resources, such as the ability to upload event logos, shareable content, and integration with social media for promotion.

Inadequate Support for Volunteering Opportunities:

Pain Point: If organizers want to recruit volunteers, a lack of information on how to do so may be a challenge.

Consideration: Include a section with information on volunteer opportunities and guidelines for recruiting and managing volunteers.

Insufficient Event Analytics:

Pain Point: Organizers may want insights into participant demographics, registration trends, or other analytics.

Consideration: Include a reporting dashboard with relevant event analytics and insights.

Architecture Flow