Meetings Web · Visual case study
Meetings
Client confidential.جهة سرية.
One meeting lifecycle, from preparation to formal approval.
01 / Context
From scattered records to one meeting system.
Organizations were holding meetings while recording minutes, recommendations, and decisions in notebooks or across separate channels. The system brings meeting setup, participants, the live session, its outcomes, and formal approvals into one connected process.
02 / My role
I designed the product from requirements to handoff.
I built the web and mobile product design from scratch, starting with the requirements and continuing through the experience, interface, and final handoff. The work covered coordinators, employees, and meeting participants with different responsibilities.
03 / The challenge
Not everything in a live meeting matters at the same moment.
The board had to support many actions during a session. Putting all of them at the same level would make the screen hard to use while people are talking and deciding.
04 / Iteration and launch
Each module improved through feedback.
We reviewed each module and feature as it was designed, gathered feedback, and refined the experience before moving forward. The system was then implemented and launched.
05 / Preparation
I turned setup complexity into an operational sequence.
Meeting basics, participants, agenda, notifications, and governance options follow the coordinator’s mental model instead of becoming one long form.
06 / Live operation
What the meeting needs now stays on top.
I ranked the board by what people use while the session is running. The video, participants, attendance, and meeting controls stay in the first view. Agenda details, recommendations, polls, questions, and files sit below, one scroll away.
This means secondary tools need a scroll. I accepted that so the core of the meeting is never buried.
07 / Role-aware simplicity
I removed administrative depth—not decision context.
The participant experience leads with what needs attention: respond, review, join, approve, and return to recent meeting records.
08 / Accountable outcomes
I designed recommendations as work—not meeting notes.
Every recommendation keeps its source, responsible people, target dates, execution progress, and status visible after the session ends.
09 / Outcome
A connected meeting system, implemented and launched.
Role-based permissions
Formal records in context
Traceable follow-up
10 / FINAL INTERFACE
Meetings. A complete product, screen by screen.
From committee setup to a lasting meeting record: explore 12 original screens from the system.
01 / MEETINGS
Meetings at a glance
Status, timing, participants and joining options sit together on each meeting card. Search and filters help people find the right session without opening every record.
02 / MEETINGS
Prepare the meeting
Meeting creation brings the session details and preparation controls into one place, giving the coordinator a clear starting point before participants join.
03 / MEETINGS
Configure the committee
Committee settings provide the organizational context around a meeting. Configuration lives in its own surface so recurring governance work stays separate from running a session.
04 / MEETINGS
Make participation explicit
The attendance link gives invitees a dedicated entry into the meeting context. Participation starts before the live session, with information and response actions kept together.
05 / MEETINGS
Run the session in context
The meeting board connects the live session with its working record. Participants, agenda items and meeting outputs remain within the same workspace as the discussion.
06 / MEETINGS
Give the discussion a formal record
The minutes experience carries the meeting beyond the live session. A dedicated document view makes the record available for review rather than leaving the outcome scattered across separate messages.
07 / MEETINGS
Keep follow-up connected
Recommendations have a dedicated surface after the meeting. The table makes follow-up work scannable and keeps the next actions connected to the discussion that created them.
08 / MEETINGS
A starting point for the secretary
The secretary dashboard brings operational information into a role-specific overview. The design gives this responsibility its own starting point within the wider product.
09 / MEETINGS
Manage the people behind the process
User management gives administrators a dedicated space to organize the people who participate in the platform, alongside the committee and meeting workflows.
10 / MEETINGS
Make access a deliberate decision
Role permissions are configured explicitly instead of being hidden inside meeting setup. This supports different levels of responsibility across administration and participation.
11 / MEETINGS
Create consistency in meeting records
Minutes templates give formal records a reusable structure. Keeping template management separate supports consistency while leaving meeting-specific content in its own context.
12 / MEETINGS
Support the whole organization
System settings complete the administrative layer around the meeting lifecycle. The product extends from individual sessions to the configuration needed to operate the platform.
