Introduction
We’re currently in the midst of a significant restructuring project for Bime Bazar. Our goal is to create a more user-friendly and efficient application. This is an ongoing challenge, as we’re working within tight deadlines and with limited resources. We’re also navigating the complexities of making these changes while the application remains operational. This article will discuss some of the key learnings we’ve gathered so far, such as the importance of effective teamwork, clear communication, and a flexible approach to our work.
Key Learnings and Challenges
A. Finding the Right Workflow:
In the past, I’ve had limited success with traditional, sequential workflows where responsibilities were rigidly defined. For example, in a previous project, UX and UI designers operated in silos, leading to delays and miscommunications. We learned that this separation hindered the design process. To address this, we’ve shifted towards a more collaborative approach where all designers are involved in both UX and UI aspects of the project. This has allowed for greater flexibility and faster iteration.
B. Collaboration and Communication:
- Design Critiques: Regular design critiques have proven invaluable. By openly discussing our work with the team, we’ve been able to quickly identify potential issues and areas for improvement. This proactive approach has significantly reduced the need for extensive rework later in the development cycle.
- Transparent Communication with PMs: Initially, we encountered challenges aligning with the product managers’ expectations. We worked with multiple product managers, each with their priorities and timelines. For instance, one PM initially requested the inclusion of a complex feature that would have significantly delayed the project and increased development costs. To address this, we actively collaborated with the product managers to prioritize features and realign expectations. We conducted joint workshops to discuss trade-offs, explore alternative solutions, and ensure everyone understood the project’s scope and constraints. We also emphasized the importance of well-defined product requirements documents (PRDs) to ensure everyone was on the same page.
- Team Spirit and Individual Growth: Fostering a strong team dynamic is essential. We’ve implemented regular one-on-one meetings to provide individual support and address any concerns. Beyond work, we’ve also encouraged social interaction by organizing team outings, such as casual gatherings for coffee or games. These activities have fostered strong bonds and a sense of teamwork, which ultimately contribute to a more productive and enjoyable work environment.
C. Project Management and Execution
- 1. Project Planning: A key aspect of our approach has been careful planning and execution. We developed a detailed Gantt chart outlining the project timeline, milestones, and dependencies between different tasks. This provided a clear roadmap for the entire team and helped us stay on track. For a deeper dive into our project planning, please refer to [Link].
- 2. Continuous Improvement: We’re continuously seeking to improve our processes by conducting regular retrospectives after each key milestone or OKR. These sessions provide a safe space for the team to openly discuss challenges, successes, and areas for improvement. By analyzing our experiences, we’ve identified and implemented several process enhancements. For example, following a recent retrospective, we implemented more frequent design critiques within the team to ensure we’re addressing potential issues early on
D. Building the Team
- 1. Finding the Right People: When I’m hiring, I look for people who are always trying to learn and grow. I believe this is crucial for building a strong and adaptable team. For more details on my hiring process, you can read [Link].
- 2. Laying the Foundation: Since our company didn’t have a design team before, we’ve had to start from scratch. This meant building a team from the ground up. Initially, it was a bit challenging to get everyone on the same page and build a strong team culture. However, we’re working hard to improve communication and create a positive work environment. You can read more about how we built our team processes in [Link].
E. Managing the Legacy System
A complete feature freeze on the legacy system was not feasible due to ongoing business needs. To address this, we’ve dedicated a dedicated designer to continue maintaining and improving the legacy application while the restructuring team focuses on the new design. This approach has allowed us to address urgent issues in the legacy system while simultaneously building the future of the application. The dedicated designer has effectively addressed urgent issues in the legacy system, while also facing challenges such as maintaining compatibility with the new application architecture. We’ve also established clear guidelines to ensure that any necessary changes to the legacy system are carefully considered and, whenever possible, incorporated into the new design.
Conclusion
The restructuring of Bime Bazar is an ongoing journey, but we’ve already learned valuable lessons. We’ve discovered the power of collaboration, the importance of open communication with stakeholders, and the critical role of effective project management. By fostering a strong team culture and continuously improving our processes, we’re confident that we’re making progress toward our goals. The insights gained from this project will undoubtedly guide our future work and contribute to the ongoing improvement of Bime Bazar.
Restructure: Insights & Takeaways was originally published in UX Planet on Medium, where people are continuing the conversation by highlighting and responding to this story.