Matrimoni
Matrimoni aimed at simplifying the wedding planning experience for couples. With our venue search feature, users can refine their venue search based on their preferences.
Product Experience
Problem Space
Problem Background
For couples getting married, weddings are a time of happiness and celebration, but planning them can also bring stress and pressure. While dreaming about their perfect day, couples have many hopes. However, weddings are often big and complex, requiring lots of decisions and budget management.
Depending on the type of wedding, they need to arrange things like the venue, food, flowers, a photographer, and an officiant. Dealing with all these details can be stressful, time-consuming, and costly. Also, there might be cultural traditions to consider, especially if your family is very traditional.
Research Insights
User Interviews
To better understand the problem and the needs of our users, we conducted user interviews. From these interviews, we found that most users needed a way to track their expenses while also collecting and organizing their ideas for the wedding. Additionally, they expressed the need for a tool that could help with vendor management and provide a detailed calendar for the days leading up to the wedding.
Many users highlighted the challenges they faced, including poor communication, a lack of simplicity, and affordability, and the desire to build better family relationships. The most challenging aspects of wedding planning were identified as
- Venue and vendor search
- Budget control
- Task management
- Communication
- Finding inspiration
Ultimately, users aim to create beautiful memories, capture happy photos, and ensure a stress-free wedding day where everything runs smoothly and tasks are efficiently delegated.
User Surveys
The survey received responses from nearly 21 participants aged 25-40, with some in the group either planning their weddings or having recently married.
Competitive Analysis
The comparison of wedding planning platforms – The Knot, The Big Day, and Planning Pod – reveals similarities in offering comprehensive planning tools. The Knot focuses on inspiration and content, featuring an appealing interface but with pricing limitations. The Big Day provides an intuitive experience and affordable lifetime subscriptions but lacks depth in inspirational content. Planning Pod prioritizes functionality, offering opportunities to expand content and improve the user interface to appeal to a wider audience.
Secondary Analysis
The collection of the following sources provides a comprehensive view of wedding planning, addressing challenges and innovative solutions. Rushali Attal's project aims to create an intuitive wedding planning system that bridges the gap between planners, couples, and guests, enhancing the planning experience. Haley Sprankle's article introduces practical apps, such as Airtable, Trello, and Discord, to streamline wedding coordination. Additionally, Selena Hoy's exploration of Japanese wedding traditions highlights the harmonious blend of ancient customs and modern adaptations, emphasizing the significance of family and friends in the journey.
In essence, these sources collectively illuminate the diverse facets of wedding planning, from technological advancements to cultural nuances, offering practical tools and a deeper understanding of the cultural richness that makes each wedding a unique and memorable experience.
User Pain Points
After speaking with users and gathering survey responses, we've identified the following pain points:
- Users frequently encounter difficulties in locating suitable venues and vendor options when planning their weddings, leading to frustration and increased planning time.
- The absence of a unified tool for collaborative budget tracking, task management, and idea sharing has resulted in challenges during wedding planning, as the couple seeks a solution that streamlines their efforts and reduces cognitive load.
Feedback
From our user research, we identified recurring themes and points of frustration among our users.
Venue and Vendor Challenges:
- Users often struggle to find suitable venues and vendors, causing frustration and delays in the wedding planning process.
- Difficulty in locating options leads to increased planning time, hindering the efficiency of wedding preparations.
Input and Budget Tracking:
- A desire for a feature enabling input and assistance with budget tracking.
- Keeping track of the budget is a recurring concern.
Task Management and Organization:
- Need for a task management system with categorization (done, in progress, upcoming).
- Desire to create to-do lists and streamline task planning.
Solution Explanation
Following our user research, we opted for two key features. The first feature is the venue search, which permits users to search for venues without requiring a login. If users wish to save their searches, they can log in. The second feature is a budget planning tool that enables users to calculate their budget. More advanced features are available to logged-in users, allowing them to save their budget calculations.
User Persona
After finalizing the features, we developed two user personas. The first persona is Krystal, a 27-year-old seeking wedding planning services that prioritize client satisfaction. Krystal's frustrations include difficulty finding dress vendors, challenges in locating suitable venues and vendors, struggles with budget and task management, and reliance on vendor checklists. Her primary goal is to efficiently find ideal venues and vendors for her wedding to align with her vision.
The second user persona is Tom, aged 30. Tom envisions a joyful and efficient wedding celebration within a tight timeframe of six months or less. He faces frustrations related to budget communication, venue, and vendor search challenges, and coordinating a wedding with a spouse in a different country. Tom is searching for an app that allows him to efficiently discover suitable venues and vendors while focusing on budget and task management. For this project, we are moving forward with Krystal.
Pivot
Initially, we planned to develop two features: 1) a venue finder and 2) a budgeting tool. However, due to time constraints and technical feasibility, we were unable to work on the budgeting tool. Consequently, we decided to channel all our efforts into finalizing the venue feature, which itself comprises multiple sub-features. As a team, our primary objective is to deliver a fully functional feature that offers a clear representation of our Minimum Viable Product (MVP).
How does “Find a Venue Feature” work?
- Users land on the landing page with two options: the "Find a Venue" button in the hero section or the same option in the navigation bar.
- Clicking the "Find a Venue" button takes users to a venue search screen for different cities.
- Users can apply filters based on their preferences and view the search results.
- To save the search, users must click the "Save Search" button, which requires them to log in.
- Users can click on any venue in the search results to access a page with venue descriptions and service details.
- Clicking the "Request Quote" button on the venue page takes users to a contact form.
- Users complete the form, submit it, and receive a confirmation of submission, marking the end of the task.
Lofi & Hifi Mockups
Iterative Design Learnings
Based on usability testing feedback:
- 80% of users found the design to be user-friendly, with positive perceptions of its simplicity, appealing layout, appropriate color choice, and clear text.
- However, 20% of users suggested that the design might have a more feminine feel and could experiment with color options.
- Users also pointed out some confusion on the landing page and inconsistencies on the "Find a Venue" page.
- Valuable suggestions from users included adding catering options suitable for vegetarians, vegans, and those with allergies, as well as providing a map or landmark for directions.
- Overall, feedback was largely positive, and with minor adjustments, we can create a more intuitive interface. A visual feedback summary is available for reference.
Implementation Details
Technical implementation
Where is it hosted?
https://matrimoni.vercel.app
What is your tech stack?
React, TailwindCSS, Material-UI, Flask, High-level journey of a request
Technical challenges
What was the hardest part of development?
Dealing with unclear design features and coordinating with team members at different times. The app concept for searching for venues based on location requires complex calls to several API services, which will be costly and need time to implement. We instead decided to generate fake data and use an image search API. While the design looks decent, sticking with the same project idea after the PM left is quite the challenge in defining what should be done and what is possible.
Does your app have any scaling issues?
To scale/have this be an actual app, we will need to gather our own venue data or pay for an API.
What are some key takeaways?
Adaptability:
- Learning to adapt to unforeseen circumstances, like the departure of the product manager, and being flexible with the project's approach allowed for continued progress despite hurdles.
Technical Proficiency:
- Gaining hands-on experience with a diverse tech stack, including React, TailwindCSS, Material-UI, and Flask, and understanding the journey of a request in a web application.
Team Coordination:
- The importance of clear communication and coordination among team members, especially when dealing with vague design features and working in different time zones.
Problem-Solving:
- Creative problem-solving skills were honed when faced with complex or costly technical challenges, such as generating fake data and using an image search API instead of making complex calls to several API services for venue location searches.
Project Scoping:
- Understanding the importance of clear project scoping and having a well-defined goal, especially when initial plans change, to keep the project on track and team members aligned.
Data Management:
- The necessity of having access to accurate and comprehensive data for the app’s functionality, and the challenges associated with data collection or acquisition through APIs when looking to scale the application.
User-Centric Development:
- Maintaining a user-centric approach in development, even when technical or structural challenges arise, ensures the final product aligns with user needs and expectations.
Learning from Feedback:
- The value of feedback, both from team members and the boot camp structure, in refining the process and understanding areas for improvement in both the project and personal or team development methodologies.
Future Steps
We won't be continuing this project currently because it would be highly time-consuming, and the required research and funding could be extensive. We have gathered insights from interviews and discussions with potential vendors, and it's evident that this task would require more resources and financial support. Collecting additional venue data would be a significant time and effort investment, and given our varied schedules, further development would be extremely challenging.
While our decision might change in the near future, this is our current team position. If we do decide to proceed, we have preliminary plans for creating a budgeting tool and generating revenue by registering venue vendors on our application.
Learnings
Product Manager Learnings:
Jolomi
This boot camp is my first ever as someone transitioning into product management. I joined a few weeks into the program and I have learned enough from this experience.
I came in to take over from the last product manager who had to withdraw from the program. This meant I had to spend my first week trying to meet the team and catching up on so many folders and data of information, which was a bit overwhelming, but I saw it as a challenge and I was able to catch up. My team members Hyun Tae, Jose, and Ammara were super helpful.
I have learned how important communication is and even at times, I fell short of communicating effectively which led to a few delays. Providing updates to the team and keeping everyone in the loop has been so important. Some days were very tough and frustrating, but a good number of days were great and all in all, I was thankful for both because every day was a lesson in itself.There is so much to think about when building a product, no matter how small, having to take time to understand what exactly you want the impact of your product to be opens up a lot of opportunities as well as issues. User feedback provided more insight on things our biases
Designer Learnings:
Ammara
Through my first team project, I've gained a profound understanding of the essential roles that clear communication, effective leadership, and collaborative teamwork play. In remote work environments, clear communication is indispensable, and I've grown to appreciate its value even more.
In the second week of the boot camp, our product manager had to withdraw from the program, leaving the team to tackle the challenge of working on his chosen product. While our team occasionally grappled with the absence of strong leadership, I took the initiative multiple times to ensure we remained on track, often staying ahead of our schedule. I see this experience as an opportunity for both personal and team growth.
Collaborating closely with developers underscored the significance of understanding feasibility. Throughout this journey, I've explored various design concepts and their practical implications. There were moments when I needed to make adjustments and let go of certain features due to constraints like feasibility and time limitations. My boot camp experience has opened my eyes to the vast world of design and development, and I've only scratched the surface. I'm excited to continue refining my skills in this area.
Balancing a substantial design workload while actively contributing to research efforts has provided me with invaluable insights. While these eight weeks were undoubtedly challenging, they were entirely worth it. Working with people with different approaches, perspectives, and learning styles was all part of the package. As a team, we encountered conflicts, sometimes stemming from inadequate communication, resulting in misunderstandings. These situations highlighted the significance of conveying my thoughts clearly and in a proper fashion.
I'm grateful for the experience and the people I've had the opportunity to work with. They have been my teachers, and I'm excited to apply these learnings in future projects. I eagerly look forward to putting these lessons into practice, as they have not only enriched my experience but also boosted my confidence in taking on new challenges.
Designer Learnings:
Jo Sturdivant
- Adapting to an Established Team: Joining the team in week 6 of 8 was challenging, as I had to quickly adapt to existing workflows, dynamics, and goals. This mirrors real-world situations where you often integrate into teams mid-project, and flexibility is essential.
- Work-Blocking for Efficiency: With only two weeks to complete the project, I learned the importance of a structured work-blocking system. This approach allowed me to manage my time effectively and meet deadlines under pressure.
- Making Data-Driven Design Decisions: Unlike my past projects, I had to rely on research conducted by others. This was a valuable experience in using pre-existing data to guide design decisions, helping me focus on the core insights without starting from scratch.
Developer Learnings:
Hyun-Tae
Needed to come up with numerous workarounds in order to make this app. Handled the git flow, the app architecture, and the Trello project board, and restructured my daily schedule to work with my codeveloper. There needs to be a clear requirement that needs discussion from the client/PM to the designer to the developer. In our case, since our PM left our designer came up with various requirements as she created the prototype.
Designs can be pumped out, while code cannot be produced as rapidly for a search engine app. I enjoyed working with my team members, but the structure of this boot camp doesn’t account for technical debt, nor could I have clear communication and receive help remotely through written/recorded messages.
Developer Learnings:
Vanady Beard
&
As the back-end developer, I learned how important it is to create efficient and reliable systems that support the entire application. This experience also taught me the importance of optimising the database and ensuring the backend is scalable and easy to maintain.
Developer Learnings:
Stephen Asiedu
&
As a back-end developer, I've come to understand the importance of being familiar with various database systems and modules. This knowledge enables me to build diverse applications and maintain versatility in my work. I've also learned that the responsibility for making the right choices rests on my shoulders, guided by my best judgement.
Developer Learnings:
Jose
&
This apprenticeship is my first venture post-graduation from a coding boot camp. I came across this opportunity on our alumni page and decided to join. Throughout this program, I've gained a wealth of new knowledge that I hadn't encountered before. I'm pleased to collaborate with a fellow developer who brings prior industry experience to the table. Despite the absence of financial compensation, the experience has been an invaluable investment of my time.
I've consistently dedicated a minimum of 40 hours per week, seven days a week, while juggling a full-time job, teaching me effective time management and the necessity of making sacrifices. One of the challenging parts of this program is having to work with other teammates in different time zones. I’m very grateful that my codeveloper adjusted to my time of availability so we could work together effectively. I’m genuinely grateful for my involvement in this program and would confidently recommend it to others.
Developer Learnings:
Maurquise Williams
&
- Process of Creating an MVP: Developing a Minimum Viable Product (MVP) taught me how to focus on delivering core functionalities balancing between essential features and avoiding scope creep.
- Collaboration in a Real-World Tech Setting: This experience taught me how to collaborate efficiently in a fast-paced tech environment, keeping the team aligned and productive, even while working remotely across time zones.
- Sharpening Critical Thinking and Problem-Solving Skills: This experience honed my ability to think critically and solve problems efficiently. By tackling challenges and finding quick solutions, I sharpened my decision-making and troubleshooting skills in a dynamic, real-world setting.
Developer Learnings:
Jeremiah Williams
&
All in all this experience was very awesome I learned that in coding with others being transparent is key
Developers Learnings:
Justin Farley
&
I learned how important communication is when working with a team. Communication provides understanding, advice, ideas, and much more. While working with the product team, I’ve found that communication keeps everything flowing smoothly. Working with a team also showed me that every member brings something different to the table and we all have to work together in order to align and meet our end goal.
Full Team Learning
In our collaborative team journey, we've uncovered the significance of effective communication and the strength derived from working harmoniously. Overcoming initial challenges brought about by role transitions, our collective effort has proven essential. We've grasped the importance of transparent communication, the profound impact of our work, and the valuable insights drawn from user feedback.
Mentorship has played a pivotal role in our team's development. Whether in design or development, we've internalized the value of clear communication, team collaboration, and adaptability. Operating across diverse time zones has broadened our horizons, exposing us to an array of perspectives. Equipped with these invaluable lessons, we are poised to navigate future projects with the diverse insights of our team members.