Saturn CoPlanner App

Solutionising

Now that we know what we want from the solution, let’s start diverging on how we can solve this! I first made flowcharts of main flows There were initially 10 flows that have been extracted and can be possible, however we only went with the 4 main ones listed below. I then broke down the action into segments, related pain points and then what opportunities or the approach I can use to solve them. Here they are:

1. Meeting Recording Flow

This flowchart details the end-to-end process for recording meetings, from setup to processing. It addresses compliance concerns with sensitive segments handling, participant consent, and clear UI warnings. The flow ensures proper documentation with auto-tagging speakers, timestamped action items, and unified storage that links records to client profiles for easy retrieval.

Lofi Screens

Here are the wireframes I have created according to what we need. On the left would be the home screen, where the adviser would be able to see all their meetings for that day and in the future. They can prepare for the meeting with a feature we can call meeting prep.

Meeting Prep

The problem of the adviser not getting time to get an idea about the client's circumstances gets solved by giving a notification before the meeting to brush up on the client. From a technical side, this was possible as the data gets assimilated through the Saturn cloud and gets sent to the adviser 10 mins before the client's meeting.

2. Past Meetings Flow (Status)

This diagram shows how users access and interact with previous meeting records. Features include visual status indicators, role-based views, advanced filtering, and full-text search capabilities. Users can review consolidated meeting details, add annotations, link meetings to tasks, and share content while maintaining confidentiality of sensitive segments.

Lofi Screens

Here are the wireframes for meeting details, this is after they have recorded a meeting and want to access the meeting recording.


Adding context

What was important and a new feature, was being able to listen to the recording, delete and share the recording if in-case a paraplanner or admin staff wanted to obtain it. It is sent to the Saturn cloud but we were recieving complaints that it should be able to be accessed by the adviser, to send it via Teams to their paraplanners and be able to add context.

3. How My Day Looks (Home)

This flow illustrates the daily scheduling experience with calendar integration. It emphasizes two-way sync with external calendars, guided scheduling, conflict resolution, and meeting labeling. Smart features include auto-notifications, pre-meeting alerts, and post-meeting actions that streamline workflow management. The red text wasn't looked into as it was a limitation from the tech-side.

Lofi Screens

Here are the wireframes for the home screen where the adviser would land. We wanted to keep this contextual and be like the name suggest "CoPlanner". It should help you with your needs. Hence, we made it extremely simple with whatever the adviser needs access to would be available and timed.

Next Best Action

This contextual feature intelligently suggests the most important task for the adviser to focus on next. By analyzing client data, meeting schedules, and outstanding actions, it provides timely prompts that improve productivity and ensure critical client needs aren't overlooked.

Calendar View

The condensed calendar view offers a space-efficient way to display upcoming meetings. The swipe-up gesture reveals more detailed scheduling information, balancing at-a-glance awareness with comprehensive planning capabilities when needed.

Prominent Record Button

Positioning the record button front and center prioritizes the core meeting documentation functionality. By relocating less frequently used navigation elements, the design emphasizes the primary action of capturing meeting details, making it immediately accessible during client sessions.

Now that we have the basics of what features we’re building along with the flows, let’s jump into making wireframes.

wireframes of possible features and solutions. At this step, we make sure that the app is functionally right. Not looking into the aesthetics so we can iterate fast! This step is crucial to decide what we're going to make. This is where we explore more features from the tech-side to see what's possible and what isn't. For example,

1 feature we couldn't get working due to a tech limitation was the adviser getting live updates on the meeting status and if they've covered all the agenda points and any remaining points they have to cover.

Bringing it all together

I took this time to diverge on the different styles that could be made. Even though Saturn does have a visual language, Saturn CoPlanner needed a new identity that was also familiar. I wanted CoPlanner to be more physical. Layers that show that it's a mix between physical and digital. Here are a few design languages I explored after scouring Pinterest for ideas.

	The design prioritizes meetings as the central user experience. Every element—from the prominent record button to contextual meeting prep insights—creates a focused environment where client sessions become the gravitational center. The 3D visual treatment draws attention to upcoming meetings and preparation tools, ensuring advisers always have the right information at the right moment.
Lots of meetings with the developers to know what’s feasible and what isn’t. Some very fuzzy pictures cz I was focusing on the process. Some features that I would have loved our users to have got pushback due to a lack of time.

Documentation and Handover

Once the use-cases and documentation was complete, it was time to handover the designs to the dev team that needed to convey the product designs.