<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Saurav Chhangani on Medium]]></title>
        <description><![CDATA[Stories by Saurav Chhangani on Medium]]></description>
        <link>https://medium.com/@saurav.design.n.edits?source=rss-949683fb9fc7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*vyT3GmfYgEM8zwbF54Dp_g.jpeg</url>
            <title>Stories by Saurav Chhangani on Medium</title>
            <link>https://medium.com/@saurav.design.n.edits?source=rss-949683fb9fc7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:14:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@saurav.design.n.edits/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[NetworkOcean: Redesigning the Website to Reflect Its Innovative Work]]></title>
            <link>https://medium.com/@saurav.design.n.edits/networkocean-redesigning-the-website-to-reflect-its-innovative-work-dfd874a94b87?source=rss-949683fb9fc7------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfd874a94b87</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Saurav Chhangani]]></dc:creator>
            <pubDate>Sun, 09 Nov 2025 14:31:24 GMT</pubDate>
            <atom:updated>2025-11-09T14:31:24.748Z</atom:updated>
            <content:encoded><![CDATA[<p>Redesigned NetworkOcean’s website using the AIDA framework to clearly convey its underwater data center technology.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zgeLHvs9EokquOg-8ksWIw.png" /></figure><h3>Problem Statement</h3><h4>Brief</h4><p>Design a website for a company that builds underwater data centers and gives an option to it’s users to reserve compute powers/ GPUs.</p><h4>Original Site</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WY12qSqSG4YMk-JupYCwZw.png" /></figure><h4>Purpose of the Website</h4><ul><li><strong>Primary</strong> — Provide information about available GPUs and enable easy reservations.</li><li><strong>Secondary</strong> — Highlight investment and partnership opportunities.</li><li><strong>Tertiary</strong> — Explain the underlying technology and support recruitment efforts.</li></ul><h4>Areas of Improvement</h4><ul><li><strong>Visual Design</strong> — The current layout feels minimal and doesn’t fully capture the innovative and futuristic identity of the company.</li><li><strong>Content Flow</strong> — The section order could better emphasize the core benefits and clearly explain <em>what</em> the company does and <em>how</em> it does it.</li></ul><h3>Research</h3><h4>Ideal Customers</h4><p>Type of orgs who would buy</p><ol><li>AI Startups → Companies developing new AI models (e.g., a startup working on generative AI like OpenAI).</li><li>Tech Companies → Large companies that need extra GPU power but don’t want to build their own data centers.</li><li>Research Institutions &amp; Universities → Academic researchers working on AI, physics simulations, or other high-performance computing tasks.</li><li>Hedge Funds &amp; Financial Firms → Companies that use AI for stock market predictions or financial modeling.</li><li>Government &amp; Defense Organizations → Governments often rent high-performance computing resources for research and security applications.</li></ol><p>Type of people who will use</p><ol><li>AI and ML engineers</li><li>CTOs and IT managers</li><li>Data scientists and researchers</li><li>Financial analysts using AI</li></ol><h4>Competitive Analysis</h4><p>List of a few companies operating in the same domain</p><ol><li><a href="https://www.subseacloud.com/">Subsea</a></li><li><a href="https://www.hicloud.com.cn/">Hi Cloud</a></li><li><a href="https://bluebirdfiber.com/data-center/">Bluebird</a></li><li><a href="https://greenmountain.no/">Green Mountain</a></li><li><a href="https://natick.research.microsoft.com/">Microsoft Project Natick</a></li></ol><h3>Section Order</h3><p>I structured the website using the <strong>AIDA framework</strong> to guide users smoothly from awareness to action:</p><ul><li><strong>Attention</strong> — Start with a strong value proposition to immediately capture interest.</li><li><strong>Interest</strong> — Present the problem and explain how the solution addresses it.</li><li><strong>Desire</strong> — Showcase benefits, proof, and differentiators to build trust and aspiration.</li><li><strong>Action</strong> — End with clear, compelling calls to action.</li></ul><p>Using this approach, I defined the section order to naturally lead visitors toward engagement and conversion.</p><h4>ATTENTION</h4><ol><li>Hero Section</li></ol><h4>INTEREST</h4><p>2. <strong>Problem Section</strong> — Emphasizes the key challenges and inefficiencies of traditional data centers.</p><p>3. <strong>Solution Section</strong> — Showcases the outcomes and advantages achieved through NetworkOcean’s innovative approach.</p><h4>DESIRE</h4><p>4. <strong>Methodology Section</strong> — Explains the process and technology that make the solution possible.</p><p>5. <strong>Additional Benefits Section</strong> — Highlights secondary advantages that further strengthen the value proposition.</p><h4>ACTION</h4><p>6. <strong>Final CTA Section</strong> — Presents key details about the technology and current GPU availability, along with a clear call-to-action to book the service.</p><p>7. <strong>Footer</strong></p><h3>Visual Design</h3><p>Since NetworkOcean builds submersible data centers, I wanted the website to convey an underwater environment — dark, calm, and built around deep blue tones that emphasize water’s importance in the system. The dotted wave pattern from the original site was expanded into a micro-dot grid to subtly represent data flow, paired with metallic surfaces inspired by the outer hull of the submersible units.</p><h4>Iteration 1</h4><p>Initially, I was leaning toward a GPU-inspired aesthetic with circuit board patterns and a neon glow feel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VMpWqlNi98GBoKg0G8sDag.png" /><figcaption>Iteration 1 for hero section</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UM--eJ0XcBOkE9yA3ysq_g.png" /><figcaption>Iteration 1 for features section</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fRgOPzGb93dLYnj5aaJISg.png" /></figure><h4>Feedback I got</h4><ol><li><strong>Background Color</strong> — The purple tone feels too vibrant and draws attention away from the main content; it should be more subdued.</li><li><strong>Features Section</strong> — The layout of features section feels cramped, causing users’ attention to jump between cards. It lacks a clear visual hierarchy to guide the reading flow.</li><li><strong>Hero Heading</strong> — The headline is too abstract; it should clearly communicate the benefit to the user at first glance.</li><li><strong>Hero Illustration</strong> — The current illustration looks outdated and doesn’t align with the modern, tech-forward aesthetic of the brand.</li></ol><h4>Building a custom tool</h4><p>For my iteration 2, I wanted to test different dot sizes and spacing for visual clarity, I looked for a Figma plugin that could convert PNG icons into dotted patterns. Since none matched my exact needs, I decided to build my own tool using Claude and Lovable. The concept was simple enough to prototype quickly with these AI-assisted coding platforms.</p><p><a href="https://dot-pattern-generator.lovable.app/"><strong>https://dot-pattern-generator.lovable.app/</strong></a></p><h4>Iteration 2</h4><p>After the first round of feedback, I decided to move away from the maximalist approach and aim for a cleaner, more minimal design. I explored the idea of using dotted patterns to subtly represent the company’s core technology. These dots, combined with metallic textures inspired by a submarine hull, create a balanced contrast between the digital and industrial aspects of the brand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J96uOg222tw8KoWFo_fN3w.png" /><figcaption>Hero Section</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9lLXTTrz-iFZVdTkok8_FA.png" /><figcaption>Problems Section</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bYJzlRdu1Yga_APwObfwzQ.png" /><figcaption>Solutions section</figcaption></figure><p>Link for the live website 👇🏼</p><p><a href="https://networkoceansite.framer.website/"><strong>https://networkoceansite.framer.website/</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfd874a94b87" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[FutureClinic: Designing a Treatment Planning App for Busy Doctors]]></title>
            <link>https://medium.com/@saurav.design.n.edits/futureclinic-designing-a-treatment-planning-app-for-busy-doctors-47c9907288ad?source=rss-949683fb9fc7------2</link>
            <guid isPermaLink="false">https://medium.com/p/47c9907288ad</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[doctors]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Saurav Chhangani]]></dc:creator>
            <pubDate>Fri, 01 Aug 2025 13:05:18 GMT</pubDate>
            <atom:updated>2025-08-02T03:44:20.433Z</atom:updated>
            <content:encoded><![CDATA[<p>A mobile-first tool to help doctors plan treatments, track appointments, and automate patient communication with ease.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3L5c4rqH2aUmgPL81pXabw.png" /><figcaption>Cover Image</figcaption></figure><h3>Context and Rationale</h3><h4>Context</h4><p>Busy doctors who treat multiple patients daily often struggle to keep track of upcoming appointments and pre-appointment action items such as lab results. Certain procedures depend on these results before the next step can begin. While some doctors rely on assistants, managing schedules, sending reminders, and following up with patients is still largely manual and easy to miss.</p><h4>Why This Problem</h4><p>I chose this problem because I’ve seen it firsthand. My sister, a dentist, often spends her Sundays planning the week ahead, calling patients to confirm appointments and request reports. I wanted to explore how thoughtful design and AI could reduce this manual load and help doctors better coordinate patient care.</p><h3>Research</h3><p>Through conversations with my sister (a practicing dentist) and her colleagues, I mapped out the typical flow of how treatment planning is handled in real-world clinics:</p><ol><li><strong>Initial Consultation :</strong> Doctors begin with a consultation and suggest 2–3 treatment options based on the patient’s condition.</li><li><strong>Standardized Plans :</strong> Once a treatment is selected, a step-by-step plan is created, most patients with similar conditions follow the same structure.</li><li><strong>Staggered Scheduling :</strong> Only 1–2 appointments are scheduled at a time, even if the full plan is known.</li><li><strong>Frequent Changes :</strong> Appointment dates often change last minute based on patient progress or availability.</li></ol><h3>Solution Overview</h3><h4>Defining the Project Scope</h4><p>Before starting the design, I outlined the full range of features the app could support and categorized them into must-haves and should-haves. This helped me focus on the core workflows doctors need most — like scheduling, reminders, and messaging, without getting distracted by nice-to-have features early on.</p><h4>Must-Have Features</h4><p><strong>1. Patient Detail Management<br></strong>Ability to add and edit patient information like name, contact, age, procedure, treatment plan, and appointment details.</p><p><strong>2. Appointment Overview<br></strong>A task-manager-style view showing all upcoming appointments sorted by date.</p><p><strong>3. Message Templates<br></strong>Option to create reusable templates for common patient messages.</p><p><strong>4. Patient Communication<br></strong>Sending reminders, caution notes, follow-ups, and medication messages directly to patients.</p><h4>Should-Have Features</h4><p><strong>1. Chat Interface</strong> <br>A chat interface for direct communication with patients</p><p><strong>2. Treatment Plan Templates</strong> <br>Option to save common treatment structures as reusable templates. (Based on primary research: Many doctors follow similar steps for half their patients.)</p><h4>Scoping Decision</h4><p>For this project, I chose to focus only on the must-have features to keep the app lean, purposeful, and within the defined timeline.</p><h4>Information Architecture</h4><p>I mapped out the key categories of information required to ensure the system runs smoothly and supports all critical workflows.</p><p><strong>Overview</strong><br>After the initial consultation, the doctor creates a treatment plan based on the patient’s condition. A treatment plan consists of multiple steps, each represented by a scheduled appointment with the doctor.</p><p>Each appointment can include the following details:</p><p><strong>1. Date &amp; Time<br></strong>When the appointment is scheduled to take place.</p><p><strong>2. Patient Message<br></strong>A message sent before or after the appointment. This could be a reminder, follow-up, or caution note.</p><p><strong>3. Doctor Reminder<br></strong>An internal reminder for the doctor, such as checking lab results before the appointment.</p><p><strong>4. Step Name<br></strong>The specific name of the treatment step (e.g., “X-ray Review”).</p><p><strong>5. Treatment Name<br></strong>The overall name of the treatment plan (e.g., “Root Canal”).</p><p><strong>6. Notes (Optional)<br></strong>Additional context or instructions related to the appointment</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ml4qhMubWRlkUQ68D9UIZQ.png" /><figcaption>Visual representation of IA</figcaption></figure><h3>Iterations</h3><h4>Home screen card</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SfTGVd7_dbEXF7CocaOtYg.png" /><figcaption>Home screen card iterations</figcaption></figure><h4>New Patient Entry</h4><p>Initially, I planned to collect scheduling details through a structured form divided into three sections:</p><p><strong>1. Patient Details<br></strong>Name, age, gender, ailment, and contact number.</p><p><strong>2. Treatment Details<br></strong>Number of steps, reminders, appointment dates and times, and optional notes.</p><p><strong>3. Notification Details<br></strong>Messages to be sent before or after each step — appointment, follow-up, and caution messages</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V2pr1Xhwne1gdFe55TLI7Q.png" /><figcaption>V1 of new patient entry flow</figcaption></figure><p>After receiving feedback, I realized that showing all fields at once could overwhelm users. To address this, I shifted to a chat-based input flow, where details are collected gradually, with contextual tables appearing for each category and for editing, the interface shows all filled-in information upfront, allowing for quick review and changes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2aKSr8iIcLexGn0bw6K_0w.png" /><figcaption>V2 of new patient entry flow</figcaption></figure><h3>Final flows</h3><h4>1. Onboarding flow</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SxWtQbBft01DWiWZqlbatw.png" /><figcaption>Onboarding flow</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3GhWFTcGoI6w17l9B9yrYQ.png" /><figcaption>Onboarding flow - walkthrough</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0d6L_7g960knmZF1dFEv7Q.png" /><figcaption>Onboarding flow — sign up</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A6yqrodmRamM1pFk8y3q-w.png" /><figcaption>Onboarding flow — login</figcaption></figure><h4>2. Treatment plan creation flow</h4><p>This flow can be accessed by clicking on plus button on home screen</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F1105796808%3Fapp_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fvimeo.com%2F1105796808&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F2042402507-0c1aaf1b3e44cb93e33170b5818a9f275e84ca30b36fc257cbb99619908d7f86-d_960%3Fregion%3Dus&amp;type=text%2Fhtml&amp;schema=vimeo" width="1080" height="2416" frameborder="0" scrolling="no"><a href="https://medium.com/media/c7bab61ca017695b5ab1895ebbd5ad02/href">https://medium.com/media/c7bab61ca017695b5ab1895ebbd5ad02/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J3SPjMWwEt38fwfvGxyN1w.png" /><figcaption>Input flow — simplistic</figcaption></figure><h4>3. Treatment plan edit flow</h4><p>I initially planned to use the 3-step flow for input, but later shifted to a chat-based approach. The original flow is now used for editing, where pre-filled info makes it easier to review and update.</p><p>This flow can be accessed by:<br>1. Tapping the edit icon on the home screen card<br>2. Selecting “Edit” from the patient details page</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yN_9AfzViuk4noqefwIq9Q.png" /><figcaption>Edit plan flow</figcaption></figure><h4>4. Template message creation flow</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oiyZzLxv1MmqISiUaZ3wWA.png" /><figcaption>Message template creation flow</figcaption></figure><h3>Other Key Screens</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mnrq3hMsOa6aDkFKO7uQzA.png" /></figure><h3>Conclusion</h3><p>Messages are sent to patients via SMS or WhatsApp, depending on clinic preference. This ensures high delivery and response rates, especially in the Indian context where WhatsApp is widely used.</p><p>Messaging is supported via standard SMS APIs or WhatsApp Business APIs, both of which are commonly used by healthcare providers for patient communication.</p><p>Try the prototype of the app linked below</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Dcdn.embedly.com%26embed_origin%3Dcdn.embedly.com%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FRLhqeQzgA724eUZgClmGoN%2FAssignment-3---Saurav-Chhangani---OpenClinic%3Fpage-id%3D2207%253A5315%26node-id%3D2241-6979%26p%3Df%26viewport%3D-5%252C141%252C0.06%26t%3D4e4wTjsmSLvQRCLr-8%26scaling%3Dcontain%26content-scaling%3Dfixed%26starting-point-node-id%3D2241%253A7012%26show-proto-sidebar%3D1%26hide-ui%3D1&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FRLhqeQzgA724eUZgClmGoN%2FAssignment-3---Saurav-Chhangani---OpenClinic%3Fpage-id%3D2207%253A5315%26node-id%3D2241-6979%26p%3Df%26viewport%3D-5%252C141%252C0.06%26t%3D4e4wTjsmSLvQRCLr-8%26scaling%3Dcontain%26content-scaling%3Dfixed%26starting-point-node-id%3D2241%253A7012%26show-proto-sidebar%3D1%26hide-ui%3D1&amp;image=https%3A%2F%2Fwww.figma.com%2Ffile%2FRLhqeQzgA724eUZgClmGoN%2Fthumbnail%3Fver%3Dthumbnails%252F5603ed3a-0535-440f-9179-ef33e9eefbde%26t%3D4e4wTjsmSLvQRCLr-8&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/ff0b4bcf2c038522106fa296bf9b00a0/href">https://medium.com/media/ff0b4bcf2c038522106fa296bf9b00a0/href</a></iframe><p><strong>Thanks for reading!</strong><br> I’d love to hear your thoughts or feedback on this case study.<br> Feel free to connect with me:</p><p>✉️ <a href="http://saurav.design.n.edits@gmail.com/"><strong>Email</strong></a> | <a href="https://www.linkedin.com/in/saurav-chhangani/"><strong>LinkedIn</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47c9907288ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>