Evolving the Connections Platform: Tools & Calendar
Project Overview
As Connections matured, our team identified a need to restructure the original "Plan" section to better serve users with expanding functionality. I led the transformation of this feature into two distinct yet complementary sections: "Tools" and "Calendar."
The redesigned Tools section enhances the user experience by integrating both familiar and new elements. Users can still track their recovery journey through the popular progress visualization graph, while accessing an expanded suite of customized surveys and recovery resources—all organized in a more intuitive interface.
The dedicated Calendar section addresses a critical need for time management in recovery, providing clear visibility of upcoming appointments, support group meetings, and medication reminders. This separation creates a more focused experience, allowing users to plan their recovery journey with greater clarity and purpose.
This strategic division not only accommodates the platform's growing complexity but also improves user engagement by presenting related functions in contextually appropriate spaces.
This Project's Design Process
Why are we redesigning
Connections' Plan?
O
Connections' "Plan" served as a central hub in the patient recovery journey. This multifunctional space contained essential recovery tools that were able to set reminder, schedule meetings, visualize their weekly & monthly progress, and countless resources of surveys. Thus making "Plan" one of Connections widely used support system.
However as Connections matured, our team identified a clear need to restructure this foundational section to better serve users with expanding functionality. The growing complexity of the platform demanded a more specialized approach to feature organization.
Research Approach & Establishing the Project Goals
I conducted an analysis of Connections' information architecture to understand how it fit within the ecosystem. This was crucial for me to identify the pain points and improvement opportunities. Based on my research, I established 3 strategic objectives to guide this project.
increase user engagement
Creating more focused, specialized sections that would draw users deeper into the recovery tools.
simplify navigation and reduce cognitive load
Reduce cognitive load by addressing the application's tendency toward feature bloat.
ensure implementation feasibility
Deliver innovative solutions, maintain existing visual consistency. Feasible to implement
The research to the challenge question
How might we evolve Connections' integrated "Plan" section into a more specialized experience that maintains its essential recovery support functions while accommodating the platform's increasing complexity and expanding feature set?
Ideation & Concept Development
The Calendar component became my initial focus due to its straightforward functionality and feature requirements. For larger scope projects, I follow a more systematic approach. This allows me to develop concepts that are both innovative and practical.
My process began with a comparative analysis; studying established calendar applications to identify successful patterns and opportunities for practical ideas. The research provided valuable inspiration while helping me understand user expectations for calendar interfaces in health-related contexts.
Eventually, I've come to realize a lot of the features of Calendar is okay. Aside renovating a lot of the UI in specific to look more clean and new. There were some oddities in the flow but it wouldn't make sense to spend so much time on something that isn't entirely affecting the overall Calendar experience. Thus I focused on cleaning up the Calendar, creating new modals, and small scale interaction changes.
Old Calendar
Navigating Complex Design Challenges
The Tools section presented significantly greater complexity than Calendar. It required me to balance innovative thinking with practical implementation constraints. While standard surveys and journaling components followed established patterns, two particularly complex survey requirements demanded creative problem-solving.
These challenging surveys initially seemed counterintuitive from a user experience perspective, prompting me to engage in more in-depth discussions with stakeholders. After thoughtful discussion about business requirements and user needs, I recognized the necessity of these components despite their complexity. Rather than pushing back, I embraced the challenge of making them intuitive despite their inherent complexity.
Concept Development: From Exploration to Conversation Starter
Following extensive brainstorming and research efforts, I developed the first conceptual iteration of the redesigned Tools and Calendar. Calendar was the easiest and quickest to reach completed state. However, these initial concept served as a conversation starter. Tangible visualization of possibilities designed to elicit meaningful feedback and spark productive discussions among stakeholders.
First few mock-ups of the Calendar
While not all of the mock-ups here. However, I found that from this meeting. There was a lot of discussion for improving the homescreen of the Tools page. They wanted me to create something a bit more "exciting" and include the progress graph in the first page.
While not all of the mock-ups here. However, I found that from this meeting. There was a lot of discussion for improving the homescreen of the Tools page. They wanted me to create something a bit more "exciting" and include the progress graph in the first page.
First few mock-ups of the Calendar
While not all of the mock-ups here. However, I found that from this meeting. There was a lot of discussion for improving the homescreen of the Tools page.
They wanted me to create something a bit more "exciting" and include the progress graph in the first page.
Stakeholder Collaboration & Technical Validation
Following stakeholder feedback, I engaged with the development team to validate the technical feasibility of my newer design concepts. This collaboration ensured my proposed solutions were both user-centered and implementable within our technical constraints. The majority of designs received positive feasibility assessments, confirming that the core functionality could be successfully developed.
Armed with validated concepts and refined requirements, I proceeded to create detailed mockups and final illustrations. This iterative process—moving from stakeholder input to technical validation to polished deliverables—ensured that the final designs balanced user needs, business requirements, and development realities effectively.
Refined Concepts to Final Deliverables
These are the landing pages of the two new redesigned sections of the application. At the end, it came out more modern and less confusing to engage with.
Journal Entries
Users will be able to compare and view their spending habits throughout the month. The user will be able to select a button that will allow them to start investing
Surveys & other tools
Individuals will have the opportunity to select a button to locate them to a page that will automate the process of distributing their deposit of money into three categories of needs, wants and savings.
Graph to Visualize Progress
Individuals will have the opportunity to select a button to locate them to a page that will automate the process of distributing their deposit of money into three categories of needs, wants and savings.
Set up reminders and meetings with your advisor
Individuals will have the opportunity to select a button to locate them to a page that will automate the process of distributing their deposit of money into three categories of needs, wants and savings.
After Project Reflections
This project highlighted key areas for professional growth, particularly in design-to-development communication. I recognized the need to better bridge the gap between design intent and technical implementation, leading me to explore enhanced prototyping methods and video documentation as communication tools.
I also developed stronger problem-solving skills when facing design challenges. When initially struggling with complex concepts, seeking input from developers not only provided technical insights but significantly boosted my confidence in the design process. This experience reinforced the value of cross-functional collaboration and taught me to leverage team expertise when navigating uncertainty.
Projects
Project One
Project Two
Project Three