<?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 Ivan russier on Medium]]></title>
        <description><![CDATA[Stories by Ivan russier on Medium]]></description>
        <link>https://medium.com/@ivan0russier?source=rss-41f114cb0aee------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*wCX9eFs-Me_mdD2sqtbawg.jpeg</url>
            <title>Stories by Ivan russier on Medium</title>
            <link>https://medium.com/@ivan0russier?source=rss-41f114cb0aee------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 22:45:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ivan0russier/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[Saving the sale]]></title>
            <link>https://medium.com/@ivan0russier/saving-the-sale-920989c68233?source=rss-41f114cb0aee------2</link>
            <guid isPermaLink="false">https://medium.com/p/920989c68233</guid>
            <dc:creator><![CDATA[Ivan russier]]></dc:creator>
            <pubDate>Mon, 08 Jun 2026 17:45:13 GMT</pubDate>
            <atom:updated>2026-06-08T17:45:13.366Z</atom:updated>
            <content:encoded><![CDATA[<h4>How we redesigned the moment Manor kept losing the purchase, Switzerland’s most iconic department store, one broken checkout at a time.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MyrQmElCOwTpqethqEHvpQ.jpeg" /><figcaption>A two-week omnichannel redesign for Manor: fixing the moment the purchase slips away.</figcaption></figure><p>I spend most of my days as a graphic designer and art director, so when my Ironhack cohort got to pick a final project, I went for the one that scared me a little. <strong>Manor isn’t a toy brief:</strong> it’s one of Switzerland’s biggest, most established names, with stores in nearly every city. Redesigning a slice of a website that real carries a different kind of pressure than a made-up app. I wanted that pressure.</p><p>Two weeks, a real partner, and one stubborn problem: <strong>people wanted to buy, and Manor kept getting in their way right before they did, the sale</strong> here meaning the purchase itself, the thing slipping away one screen before the end.</p><p>Here’s how we found that moment, and what I designed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rRLGliDnqCuIWB9Md-YYJg.jpeg" /><figcaption>The project at a glance: a real client, three designers, nine research sessions, two weeks.</figcaption></figure><h3>The brief: don’t reinvent Manor, refine it</h3><p>Manor is <strong>Switzerland’s largest department store:</strong> 59 stores, 100+ years of heritage, a place where you can buy a swimsuit, a sofa and a bottle of wine in one afternoon. The brand isn’t broken. The <strong>online journey</strong> is.</p><p>Our partner asked us to look at the <strong>omnichannel experience</strong>: the seams between the website, the app and those 59 physical stores. Their own hunches (checkout drop-off, too many returns, a clunky Click &amp; Collect ) turned out to be exactly where users struggled too.</p><p>So my north star from day one was restraint. <strong>The branding, the structure, the catalogue already existed.</strong> My job wasn’t a redesign for the portfolio reel, it was to remove friction from something real, without breaking what already worked.</p><blockquote>The hardest part of refining a live product isn’t having ideas. It’s having the discipline to leave 90% of it alone.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XFW99hK7Sz_0Ax2jV59JSA.jpeg" /><figcaption>Mapping the Swiss landscape: a premium brand sitting in the most fractured online journey of the set.</figcaption></figure><h3>Where Manor actually sits</h3><p>Before touching a screen, we mapped the Swiss landscape — Zalando, Globus, Galaxus, About You, and IKEA as a surprise omnichannel benchmark.</p><p>The map made the gap obvious. <strong>Manor earns a premium, curated position, but its online experience felt the most fractured of the set.</strong> Swiss shoppers are demanding: they’re quality-conscious, privacy-aware, and a broken flow reads to them as <strong>low quality</strong>, no matter how good the product is.</p><p>That gap : premium brand, shaky journey, was the brief.</p><h3>The plan broke. Good.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H73yQVf0EXXsm6ZV_BJV3g.jpeg" /><figcaption>Our two-week path, including the mid-week pivot from scripted interviews to live usability tests.</figcaption></figure><p>We ran our two weeks like a compressed double-diamond: secondary research, a CSD matrix, a stakeholder interview with Juan (Manor’s own UX designer), then users.</p><p>Then the plan fell apart. <strong>Most of the people we recruited had never actually shopped at Manor.</strong> Our carefully scripted interview guide was suddenly useless.</p><p>So we pivoted: mid-week, on the spot. Instead of asking people to “remember” Manor, we put the <strong>live site in front of them and watched them try to buy something.</strong> Think-aloud usability testing. Nine sessions in total.</p><p>It was the best accident of the project. You can’t fake the moment someone squints at a screen and goes “wait… what am I actually paying here?”</p><figure><img alt="Four frictions surfaced in every session, and Manor’s 2.5★ Trustpilot said the same in public." src="https://cdn-images-1.medium.com/max/1024/1*_8oQaHEcVPWpMc-jqKV3Ww.jpeg" /><figcaption>Four frictions surfaced in every session, and Manor’s 2.5★ Trustpilot said the same in public.</figcaption></figure><h3>Four ways Manor was losing the sale</h3><p>The same four frictions surfaced session after session:</p><p><strong>- Returns crisis:</strong> people buy three sizes to try at home and send most of it back. Sizing doubt, made expensive.<br><strong>- Cart abandonment:</strong> confidence collapses at shipping and payment, the very last steps.<br><strong>- Pricing confusion:</strong> stacked promos and crossed-out prices meant nobody could see the final number.<br><strong>- Fractured omnichannel: </strong>Click &amp; Collect exists, but it’s easy to lose, and third-party sellers hide in plain sight.</p><p>Manor’s <strong>2.5★ on Trustpilot</strong> said the same thing in public: delivery delays, surprise shipments from partners abroad, and returns that send you back to a store that can’t help you. Trust, quietly bleeding out.</p><h3>Meet Sofia</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n6_27PFltzIjx7gsoj8Eyw.jpeg" /><figcaption>Practical Sofia, the time-pressed Zurich shopper every decision had to answer to.</figcaption></figure><p>Everything we learned pointed at one person. We called her <strong>Practical Sofia:</strong> 36, Zurich, urban professional, shopping on her phone between two things.</p><p>Sofia doesn’t shop for fun. <strong>She shops to save time.</strong> She wants to find the right thing fast, feel sure about size and price, and pick the delivery that fits her week. When something’s off, easy returns aren’t a nice-to-have : they’re the whole reason she’ll risk buying online at all.</p><p>Keeping Sofia in the room is what stopped this from becoming a list of features. Every decision had to earn its place by answering one of <em>her</em> questions.</p><h3>The lowest point</h3><p>🖼 IMAGE → journey.jpg</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y7pVvx8LSAID3bG3dG97_w.jpeg" /></figure><p>When we mapped Sofia’s journey, the shape told the story better than any slide could.</p><p>She starts <strong>curious and hopeful.</strong> She finds a shirt she likes : <strong>peak</strong>. Then the questions start: <em>which size? what’s the real price? which store?</em> And the line falls off a cliff at the exact step where Manor needs her most.</p><p>&gt; <strong>Manor loses Sofia right before the sale.</strong></p><p>That single sentence became our brief-within-the-brief.</p><h3>The problem, in one line</h3><p>After all the research, we boiled it down to this:</p><blockquote>Manor shoppers need to find every key piece of product information and place their order <strong>effortlessly</strong>, because today the flow breeds mistrust, frustration and drop-off.</blockquote><p>Notice it’s not about adding things. It’s about “<em>removing reasons to hesitate.”</em> That framing drove every screen that followed.</p><h3>My approach: answer her questions before she asks them</h3><p>I was hands-on across the UI and the issue-hunting, and I <strong>designed the two screens where it mattered most: the product page — where most of the friction surfaced, and the delivery step.</strong> (Research and synthesis were a three-person effort with Alyne and Alexandre.)</p><p>I gave myself one rule: <strong>surface the information that made Sofia hesitate, size, price, who’s selling, how she gets it: right where her eyes already are.</strong> No new pages. No clever features. Just clarity, in the places confusion used to live.</p><p>We pulled the backlog through a MoSCoW pass to protect that focus, then built lo-fi → mid-fi → hi-fi <em>inside Manor’s existing system.</em></p><h3>Decisions: the product page</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CyQuJeqM9pHdLVcvWa1oKQ.jpeg" /><figcaption>Product page, before → after: surfacing size, price, colour and reviews where her eyes already are.</figcaption></figure><p>A few of the moves I’m happiest with:</p><p><strong>One price story, not three.</strong> The page stacked three competing sale tags. I cut them to <strong>a single −25% and one clean price</strong>, the discount already tells you it’s on sale. Less noise, more trust.</p><p><strong>Reviews, surfaced.</strong> Ratings were buried at the very bottom. I lifted them r<strong>ight beside the title</strong>, because for fashion that’s where the truth about fit and sizing lives.</p><p><strong>Colour you can see.</strong> Flat colour squares became <strong>real photos of each colourway: </strong>a preview AND an extra layer of information in a single glance.</p><p><strong>No size, no false promises. </strong>Nothing is pre-selected anymore. Try to check availability without choosing a size and you get a calm, specific nudge instead of a wrong answer: “<strong>Please choose a size to check availability.”</strong> Honest beats convenient.</p><p>I also unified the two competing add-to-cart buttons into **one CTA**, put <strong>all delivery options (home, in-store, Click &amp; Collect) as a preview directly on the page</strong>, and added a <strong>sticky CTA</strong> for the long mobile scroll: so the way to act is always one thumb away.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9a9B9e-PzIHsSBcyinbs8Q.png" /><figcaption>Product Page: <strong>Before / After</strong> hi-fi</figcaption></figure><h3>Decisions: the rest of the flow</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*czgIT6gOJjSalbEHYOQS-Q.jpeg" /><figcaption>Cart and checkout, before → after: clear sellers, a simpler total, and a sense of where you are.</figcaption></figure><p>🖼 IMAGE → checkout_decisions.jpg</p><p>The cart and checkout are where the sale was dying, so the whole team threw everything at them.<strong> The delivery screen was mine</strong>, and the principle there matched the product page: show the real options, and the real <em>reason</em> when one isn’t available.</p><p>Across the flow, the decisions that mattered most:</p><p><strong>Who’s actually shipping this.</strong> Vague <em>“Manor Partner”</em> became <em>“the real seller’s name”</em>, with delivery and returns grouped per vendor, the exact confusion Trustpilot reviewers kept getting burned by.</p><p><strong>From twelve numbers to four.</strong> The price breakdown repeated itself into a wall of subtotals. We collapsed it to the <strong>four lines that matter</strong>, ending on the one she actually pays.</p><p><strong>Sign in first, guest welcome.</strong> We flipped the hierarchy so <strong>signing in is the primary action</strong> (it unlocks her member price), kept guest checkout one tap away, and added “<em>create account”</em> right there, plus a little cart summary so she never loses sight of what she’s buying.</p><p><strong>Always know where you are.</strong> A persistent <strong>progress bar</strong> runs across Data → Delivery → Payment. On my delivery screen, I also killed the address overlay that used to ambush people before they’d chosen anything; now it opens only when she taps to edit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*njkzWY1HITzImkzGRh6FTA.png" /><figcaption>Check out flow: Before / After</figcaption></figure><h3>A quick word on the words</h3><p>Microcopy did a lot of the heavy lifting. A good error message answers three questions: <strong>what happened, why, and what to do next.</strong> So the availability error doesn’t scold, it points: <strong>choose a size, then I can check.</strong></p><p>Same logic on the locked <strong>Click &amp; Collect</strong> option: instead of a dead grey button, it stays visible with a “<em>why isn’t this available?”</em> explainer. <strong>Never hide a limitation, explain it.</strong> That’s how you keep trust when you can’t say yes.</p><h3>Where it goes next</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kuunNR6EDpsAMhciq9XNfQ.jpeg" /><figcaption>Three next bets : Find in Store, a size recommender, and per-item delivery, ranked by feasibility.</figcaption></figure><p>We split the rest of the backlog by what Manor could realistically ship, soonest first:</p><p>- <strong>Find in store:</strong> real-time stock, per size, per store, so Sofia never travels for an empty rack.<br>- <strong>Size, sorted:</strong>a couple of measurements and a fit preference, aimed squarely at the buy-three-return-two habit.<br>- <strong>Delivery, per item:</strong> Click &amp; Collect one piece, ship another home. One cart, two journeys.</p><h3>What Manor said</h3><p>We presented to Manor’s own UX designer, Juan, and his reaction did more for my confidence than any grade. He was genuinely impressed by how much ground three of us covered in two weeks, and, more tellingly, told us that <strong>several of the problems we’d surfaced are ones his team is actively working on right now.</strong></p><p>You can’t ask for better validation than a stakeholder saying <em>yes, that’s real, and we’re already on it.</em> It meant our research had landed on the actual pressure points, not invented ones.</p><h3>What I took away</h3><p>The thing I’m proudest of isn’t a screen, <strong>it’s how the three of us worked.</strong></p><p>We made the most of each other’s strengths and, just as importantly, we listened when we disagreed about a decision. Debating well, without ego, turned out to be the real skill.</p><p>It didn’t start smoothly. For days we couldn’t find Swiss shoppers who actually knew Manor, and it was genuinely scary: <em>how do you start a project with no user interviews?</em> So we scrambled: LinkedIn, Facebook, even Reddit. What was meant to be 5 interviews became <strong>9 sessions</strong>, and when people didn’t know the brand, we adapted on the fly into <strong>think-aloud usability tests on Manor’s live site.</strong> That improvisation became the backbone of everything — real, unguarded insights instead of polite answers. Our cohort even voted it the <strong>strongest research project</strong> of the group.</p><p>Coming from a visual background, my instinct is to make everything look resolved. This taught me the opposite discipline: <strong>show the process, the dead ends and the why, not just the polished result.</strong> And designing <em>inside</em> a brand I respect — with the restraint to fix it rather than flatten it, felt closer to real work than any blank canvas ever has.</p><p><em>Manor:UX/UI redesign · Ironhack final project, May 2026. Designed with Alyne Daus &amp; Alexandre Benard, in partnership with Manor and their UX designer Juan.</em></p><p><em>Thanks for reading.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=920989c68233" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cohort: Stop Studying Alone]]></title>
            <link>https://medium.com/@ivan0russier/cohort-stop-studying-alone-11033da8962d?source=rss-41f114cb0aee------2</link>
            <guid isPermaLink="false">https://medium.com/p/11033da8962d</guid>
            <category><![CDATA[app-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Ivan russier]]></dc:creator>
            <pubDate>Sat, 06 Jun 2026 14:34:20 GMT</pubDate>
            <atom:updated>2026-06-06T14:34:20.046Z</atom:updated>
            <content:encoded><![CDATA[<h4>A UX/UI case study about isolation, dropout rates, and the app we built to fight both.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qnVjh6toBzSoHRYNcYfLOw.png" /></figure><h3>THE BRIEF</h3><h4>We’re designing for the students everyone’s trying to keep.</h4><p>Hundreds of thousands of people enroll in online bootcamps every year. And every year, a significant number of them just… stop.</p><p>Not because the content was too hard. Because they felt completely alone.</p><p>For our Passion Project at <strong>Ironhack</strong>, my team :<strong> Michael, Alyne and I</strong>, chose to take that problem head-on. The result was Cohort: a community-first mobile app designed specifically for <strong>self-guided bootcamp students</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*sU_ZUbBEBhjkYuQffrQ2cw.jpeg" /><figcaption>The numbers that framed the problem, and the one that surprised us most</figcaption></figure><p>Those numbers tell the problem. The interviews told the story behind it.</p><h3>STARTING POINT</h3><h4>We didn’t continue where he left off. We restarted, on purpose.</h4><p>One of my teammates, Michael, had already worked on this topic in a previous bootcamp. He had secondary research, initial insights, early ideas. There was a real foundation to build on.</p><p>We could have just picked it up. Saved time. Gone faster.</p><blockquote>“We decided to restart from scratch — using the earlier work only as context, not as a path to follow.”</blockquote><p>That decision mattered more than it might look like. It meant we had to <strong>earn every insight ourselves.</strong> We came in with fresh eyes, ran our own research, formed our own understanding. The prior work became a sanity check, not a shortcut.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*xFDMBT3xrTrUne6lcdZJCg.jpeg" /><figcaption>Our 2-week sprint</figcaption></figure><h3><strong>RESEARCH</strong></h3><h4><strong>What people actually said.</strong></h4><p>30+ survey responses. 5 in-depth interviews. Real students who had been through self-guided bootcamps — not hypotheticals, not industry reports.</p><p>The process started with a Lean Survey Canvas. We generated 20–25 questions, cut them down to 15, then used the survey responses to build our interview questions. I finished building and publishing the survey solo on the first evening.</p><p>What came back in those conversations was raw. People talked about burnout, Slack channels that were “dead,” tutors who took two days to respond, and a sense that the <strong>vibrant community promised in the marketing simply didn’t exist.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J9W-YQZ-Xih22lal5muumw.jpeg" /><figcaption>Five clusters from our affinity diagram — and the one insight that connected all of them.</figcaption></figure><p><strong>52% of respondents were dissatisfied with the social aspect of their bootcamp.</strong></p><p>That number shaped everything that followed.</p><p>“Isolation and low sense of belonging erodes motivation — not lack of skill.”</p><h3>WHO WE DESIGNED FOR</h3><h4>Not archetypes. Composites of real voices.</h4><p>Two people emerged clearly from our research. We did something I’d never done before on a persona: we added personality traits. It sounds small. But it made a real difference in how we talked about design decisions — Anna and Felix felt like people in the room, not cards on a wall.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*sUrTkmIIC9QWCxy7KxE3mg.jpeg" /><figcaption>Anna needs community. Felix needs live support. Both need Cohort.</figcaption></figure><p><strong>Anna became our primary design lens.</strong> Every feature decision ran through one question: does this help Anna feel less alone?</p><h3>USER JOURNEY</h3><h4>The emotional curve told the story better than any metric.</h4><p>We mapped Anna’s experience across five stages, from the initial search for a bootcamp through barely recovering from her crisis point.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*1vE81GMxdjKDUCxopy3AXg.jpeg" /><figcaption>Anna’s journey. The drop at stage 4 is exactly where Cohort intervenes</figcaption></figure><p>The shape of that curve is the core design brief. Confidence builds in week one. Then the workload hits. Isolation peaks. She’s close to quitting.</p><p>That crisis point is where Cohort intervenes. Not with more content. With connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*E6YHtJpkLO8mMQ4E5qZSkA.jpeg" /></figure><h3>THE DEBATE BEHIND THE STATEMENT</h3><p>How broad or specific do we go? That question took longer to answer than expected.</p><p>Too specific and we’d paint ourselves into a corner. Too broad and every design decision would be up for debate.</p><p>We landed on a statement that named the who, the need, and the why — in that order. Specific enough to guide decisions. Open enough to leave room for multiple solutions.</p><h3>IDEATION</h3><h4>From Crazy Eights to must-haves.</h4><p>One round of Crazy Eights. Enough to get ideas out of our heads and onto paper without overthinking. Then MoSCoW to separate what mattered from what was just interesting.</p><p>Three sitemaps. One long afternoon of debates. The conversations were sometimes frustratingly deep — but the depth is what made every later decision feel grounded.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*MFZT88-qorWlO4pEHr5dww.jpeg" /><figcaption>MoSCoW prioritization — what made the MVP and what didn’t.</figcaption></figure><p>The principle we kept coming back to: what is the minimum viable community? Not the minimum viable product — the minimum experience that makes Anna feel she belongs.</p><h3>THE COMPETITIVE GAP</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*QkcAkN1SWdnJuIxFHYRC3w.jpeg" /><figcaption>Discord has community, Slack has comms, StudyStream has rooms, none have it all</figcaption></figure><p>The gap wasn’t subtle. No existing platform offered buddy matching, live rooms, expert access, and bootcamp-specific community in one place. That’s the space Cohort occupies.</p><h3>DESIGN PROCESS</h3><h4>This is where the process showed its shape.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*1-RbGmDOQoV7Vsto3GUDig.jpeg" /><figcaption>Lo-fi → Mid-fi → Hi-fi. The jump to hi-fi was fast because the hard thinking happened earlier</figcaption></figure><h4><strong>Lo-fi: intentionally rough.</strong></h4><p>The lo-fi stage wasn’t about beauty. It was about logic. Can a user get from A to B? Where does the flow break? We sketched directly on paper — quick, disposable, no attachment to any idea.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6lPwq61OAF57yqgSn0dLjA.jpeg" /><figcaption>Raw hand-drawn sketches, the uglier the better at this stage. No polish, all process</figcaption></figure><h4><strong>Mid-fi: where the real decisions live.</strong></h4><p>By mid-fi, we knew the visual direction we were aiming for. We may have had fewer screens than some other teams at this point. But the screens we had felt accurate. Intentional. Not just filled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H2LOnuGP7MY343sM2qzZ1A.png" /><figcaption>Mid-fi spread — 4–6 key screens. Structure and components, no colour yet</figcaption></figure><blockquote>“The ones we do have feel very accurate to what we like, what we want to build, and the style we are aiming for.”<br> — My journal, 07.05.26</blockquote><h4>Hi-fi — the reveal.</h4><p>Adding colour and polish to a well-reasoned mid-fi didn’t feel like a discovery. It felt like a reveal. The jump was fast because the thinking had already happened.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Te5u6zkmg_pMkexmN4Ar1g.png" /><figcaption>Some of the Hi-fi Screens</figcaption></figure><h3>THE SOLUTION</h3><h4>Cohort isn’t a learning tool. It’s a belonging tool.</h4><p>Five core features. Each one a direct response to something real people told us they were missing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*t8_aaJUiBqaI0PgKYYxlDQ.jpeg" /><figcaption>Five features. One mission: make Anna feel less alone.</figcaption></figure><h4>Buddy Matching</h4><p>Rather than connecting students randomly, Cohort recommends up to five potential buddies based on profile information, interests, learning goals, and existing connections. Compatibility over randomness.</p><h4>Live Study Rooms</h4><p>Avatar-based audio rooms where students can drop in and study alongside others — no camera pressure, no performance anxiety. Just presence.</p><h4>Expert Access</h4><p>1-on-1 sessions with industry mentors. Real, personalised feedback — not the “copied and pasted” responses our interviewees described.</p><h4>Super Buddies</h4><p>Experienced users who act as community ambassadors. When you join for the first time, you’re immediately connected with a few Super Buddies so your first day is never empty.</p><h4>Trophy Room</h4><p>Streaks, badges, milestones. Designed to celebrate consistency, not just completion. Showing up matters as much as finishing.</p><h3>REFLECTION</h3><h4>What I’d take into the next project.</h4><p>Two weeks is not a lot of time. But we got somewhere that felt real.</p><p>The thing I keep coming back to: the decision to restart from scratch was the right one. We earned our insights. They informed our decisions. When we were building the hi-fi, we weren’t just making it look good — we understood exactly why every feature existed, because we’d gone through the friction of figuring that out ourselves.</p><p>If I could change one thing: I’d push for earlier concept testing. We tested late. Earlier feedback could have shortened some of those sitemap debates — not eliminated them, they had value — but shortened them.</p><blockquote>“Agreeing on why you’re designing something is the hardest and most important part of any project.”</blockquote><p>The problem statement debate was slow and frustrating. But being forced to align on direction before touching Figma is what made everything after move faster.</p><p>Cohort might be a school project. But the problem is real. The people are real. And somewhere out there, Anna is still studying alone.</p><p>That’s the thing we were trying to fix.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*MTblvOeTSaHPYpg9k0MTaQ.jpeg" /></figure><p><em>Thanks for making it to the end. You clearly don’t have a dropout problem. Anna would approve.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11033da8962d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redesigning Kleinanzeigen — when less is a product decision]]></title>
            <link>https://medium.com/@ivan0russier/redesigning-kleinanzeigen-when-less-is-a-product-decision-1069a59ae87a?source=rss-41f114cb0aee------2</link>
            <guid isPermaLink="false">https://medium.com/p/1069a59ae87a</guid>
            <dc:creator><![CDATA[Ivan russier]]></dc:creator>
            <pubDate>Sun, 17 May 2026 13:16:12 GMT</pubDate>
            <atom:updated>2026-05-17T13:16:12.767Z</atom:updated>
            <content:encoded><![CDATA[<p>Germany’s most-used classifieds app has a density problem. Here’s how I diagnosed it, and what I chose to do about it.</p><h3>The choice</h3><h3>I picked the app that scared me most</h3><p>Kleinanzeigen is everywhere in Germany. Millions of listings, millions of users, a product that’s been iterated on for years — which makes it a real challenge. Popular apps are usually polished; the low-hanging fruit is gone. The design problems that survive are structural ones.</p><p>That was exactly the point. I wanted a project that would push me — something that would mean something in a portfolio. Not a niche tool with two screens, but a complex marketplace with competing priorities: sellers, buyers, ads, categories, saved items, messages. A real product.</p><blockquote><em>The complexity was the whole point. Easy projects don’t teach you much.</em></blockquote><h3>Heuristic Analysis</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wMJyUCb9oWxsI4UlpBGwlA.png" /></figure><h3>Four problems, one root cause</h3><p>I ran a full heuristic analysis across two screens — the homescreen and the “add a listing” flow — using Nielsen’s 10 heuristics as a framework. The findings pointed to the same root issue: <em>the app was trying to show everything at once, and in doing so, it communicated almost nothing clearly.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3gaNMzNHz-ujZXvVh6sADQ.png" /></figure><p>The “add a listing” flow had a different flavour of problem. Instead of visual overload, it was invisible affordances — fields that looked like static text, a category picker with no hint it was a picker, required fields that declared themselves only after you tapped submit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XHxEkFXPxbGrSBbIga0Uzw.png" /></figure><h3>Design decisions</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*52kJy49oFz_iJRSmBQPSvw.png" /></figure><h3>The choices — and the reasoning behind each one</h3><p>Every change maps to a specific problem. Nothing was restyled for aesthetics alone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*80VqMGCvU1XP1zevwtGsMA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_z9FYAJDxz96Eaw2OQnYgA.png" /></figure><h3>Feature highlight</h3><h3>The Merkliste — making saved items feel real</h3><p>The original app had a favorites function. You tapped the heart, the item went somewhere invisible. There was no feedback, no collection, no sense of ownership.</p><p>I replaced it with a swipeable strip of saved cards that appears directly on the homescreen. The idea was simple: <em>when you save something at a physical market, you pick it up. You hold it.</em> There’s a tactile sense of a collection forming before you’ve decided to buy.</p><p>The Merkliste tries to recreate that. Your saved items sit in a horizontal strip you can browse with a swipe — not a list buried in a tab, but something that feels alive on the main screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/412/1*4oZxEw9AmBoXC1f0P6gixQ.gif" /></figure><h3>A trade-off, honestly</h3><h3>One line. Condensed type. And a font I’m not entirely happy with.</h3><p>Product titles in the original app wrapped to two lines, which made the cards feel dense and hard to scan. My decision was to reduce them to one line, using a condensed typeface that could still carry a reasonable amount of text in a tight space — while keeping images large.</p><p>The function worked. The specific typeface I landed on didn’t feel right to me. It does the job, but it sits more as a placeholder than a finished decision. If I were to continue the project, I’d pair a 30-character title limit — enforced at the listing creation stage — with a more considered condensed face. Shorter titles, better type.</p><blockquote><em>The idea was right. The execution was a compromise made under time pressure. I’d rather be honest about that than pretend it was intentional.</em></blockquote><h3>Reflections</h3><h3>What I’d do differently</h3><p>I invested a lot of time rebuilding the original app screen by screen in Figma, more than was probably necessary. But it gave me something an audit alone couldn’t: I genuinely understood the design system I was working against. Every component I rebuilt told me something about the choices that had been made before me, and why some of them weren’t working.</p><p>Better upfront file organisation would have saved me real time in the final stretch. The scope was large and the structure got complex faster than I expected. That’s a process lesson I’ll carry forward.</p><h3>Key learnings</h3><h3>Three things this project made clear</h3><ul><li><strong>1 —</strong> Rebuilding teaches what auditing misses. Copying every component by hand reveals the logic , and the illogic.</li><li><strong>2 —</strong> Pick the app that scares you. A project’s difficulty is proportional to what it teaches you.</li><li><strong>3 —</strong> A placeholder is a flag, not a failure. knowing exactly what needs to change is a design skill too.</li></ul><p>Thanks for reading ✌️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1069a59ae87a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Radical Transparency: Design of a Basketball agency website]]></title>
            <link>https://medium.com/@ivan0russier/radical-transparency-design-of-a-basketball-agency-website-ba03ce0f9781?source=rss-41f114cb0aee------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba03ce0f9781</guid>
            <dc:creator><![CDATA[Ivan russier]]></dc:creator>
            <pubDate>Wed, 29 Apr 2026 19:01:01 GMT</pubDate>
            <atom:updated>2026-04-29T20:17:26.003Z</atom:updated>
            <content:encoded><![CDATA[<h3>This case study explores the design journey of <strong>B7C Management</strong>, a basketball recruitment agency website created by the <strong>Deathly Hallows</strong> team (Alexandre, Lucas, and myself).</h3><h3>The Project Overview</h3><p>The goal was to create a trustworthy e-commerce-style platform for a competitive and often opaque industry: basketball recruitment.</p><ul><li><strong>The Problem:</strong> Young French players struggle to identify trustworthy agencies in an industry perceived as exploitative.</li><li><strong>The Timeline:</strong> A fast-paced sprint, from initial research to a high-fidelity prototype.</li><li><strong>My Role:</strong> I co-conducted the research, led the first deep-dive user interview, and focused on translating insights into the final visual system.</li></ul><h3>A Designer’s Perspective: Why Over What</h3><p>We didn’t just want a “cool website” feel; we wanted to solve the <strong>trust gap</strong>.</p><p><strong>The Pivot in Research</strong> Initially, we focused on the mechanics of going pro. However, our secondary research revealed that families are often the emotional “gatekeepers”. During my interview with <strong>Mamaye</strong>, it became clear that a player’s “public vs. private” life is deeply intertwined. This insight led us to refine our problem statement: players don’t just need an agent; they need a <strong>reliable roadmap</strong> to avoid exploitation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oAYq3uOA8hQBlcAk5z3GZw.jpeg" /></figure><p><strong>Scannable Highlights &amp; Key Phrases</strong></p><ul><li><strong>Family Matters:</strong> Agencies must manage the “family gatekeeper” who often decides under emotional pressure.</li><li><strong>Transparency is the Product:</strong> Trust is built by showing the “Why” (vision) before the “What” (services).</li></ul><h3>Visual Storytelling: The Process</h3><p><strong>From Hybrid Low-Fi to High-Fi</strong></p><p>We experimented with a “hybrid” low/mid-fidelity layout. While it took longer than expected, it helped us having a good first idea of the website feel. This “fail fast” moment ensured our final high-fidelity screens felt professional and “industry standard”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lC_KUfj9hlSOSkQMhRTrQw.jpeg" /></figure><h3>The Persona: Ambitious Jason</h3><p>Our design stayed laser-focused on <strong>Ambitious Jason</strong>, an 18-year-old student in France.</p><ul><li><strong>His main Goal:</strong> Play in the USA.</li><li><strong>His main Pain Point:</strong> Suspicion toward agencies and a fear of failure.</li></ul><h3>Mockups That Shine</h3><p>We prioritized clarity over clutter. Based on usability testing, we made a crucial design choice: moving the <strong>Eligibility Test</strong> from the contact page to the Main homepage. it felt like a necessity based on our insights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WmpMq9HaHKHAIYUorGgBYg.jpeg" /></figure><p><strong>Before vs. After: The Navigation Pivot</strong></p><ul><li><strong>Before:</strong> Eligibility test buried in the scroll.</li><li><strong>After:</strong> A clear, permanent “Eligibility Test” call-to-action in the nav bar, acting as the ultimate “trust-building” tool.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4b-97RwPg-oRGB-JnO1fBw.jpeg" /></figure><h3>Personal Reflection &amp; Personality</h3><p>This project was a lesson in <strong>trust and synergy</strong>. We “divided and conquered” with total confidence in each other. My biggest takeaway? Design is 20% pixels and 80% listening — Mamaye’s interview proved that a single genuine conversation can redefine an entire project’s direction.</p><p><strong>Brand Identity: Bold &amp; Modern</strong></p><p>We chose <strong>Special Agent Expanded</strong> for headers to evoke power and professionalism, paired with <strong>Bricolage Grotesque</strong> for a modern, scannable feel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vhXq0EnvqISf06ULgCLoug.jpeg" /></figure><h3>Final Word</h3><p>B7C Management isn’t just a website; it’s a design story about giving young talents a fair shot. By prioritizing process over the end result, we created a platform that doesn’t just sell a service — it builds a future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba03ce0f9781" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wicked Problem — Urban Mobility]]></title>
            <link>https://medium.com/@ivan0russier/wicked-problem-urban-mobility-59dec5280035?source=rss-41f114cb0aee------2</link>
            <guid isPermaLink="false">https://medium.com/p/59dec5280035</guid>
            <dc:creator><![CDATA[Ivan russier]]></dc:creator>
            <pubDate>Sat, 11 Apr 2026 13:12:28 GMT</pubDate>
            <atom:updated>2026-04-11T13:12:28.776Z</atom:updated>
            <content:encoded><![CDATA[<h3>00 — Exploring the Urban mobily 🚋</h3><p><strong>I love</strong> travelling in cities using public transport — <strong>sometimes it feels like I’m the only one.</strong></p><p>I’ll take a 40-minute train over a 20-minute car ride, without hesitation.</p><p>Living in Munich, commuting is part of my daily life — and something I genuinely enjoy.</p><p>But working on this project made me realize something:</p><blockquote><strong><em>enjoying public transport doesn’t mean understanding it.</em></strong></blockquote><p>What started as a broad exploration of urban mobility quickly revealed a deeper issue.<br> Not just delays. Not just crowded trains.</p><p>But a system full of <strong>hidden friction, constant uncertainty, and small decisions that add up every day</strong>.</p><blockquote><strong><em>This project explores how people deal with city commuting : how they adapt, plan around it, and cope with it.</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/1*iObhe7I2hg7PrApN4oBb1g.png" /></figure><h3>01 — When Research Challenges Assumptions 🧐</h3><p>We expected people to complain about crowded spaces, noise, and busy streets.</p><p>But what stood out most was something else:</p><blockquote><strong><em>unreliability.</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v-JeBj9vMhrmTlqNrQ6UOQ.png" /></figure><p>Everyone had experienced delays, cancellations, or unexpected disruptions.</p><p>And instead of fixing the system, people adapt to it.</p><p>They leave earlier.<br> They double-check routes.<br> They avoid uncertainty.</p><blockquote><em>They don’t optimize —</em><strong><em> they cope.</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y9EzZZNUgOTGA7Q9sR9mqQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*An7uutVz7bkMAYrD2V-crQ.png" /></figure><h3>02 — Defining the Problem 🔍</h3><p>This led to our problem statement:</p><h4>Metropolitan commuters need a way to deal with unexpected transport issues to reduce stress.</h4><p>This became the foundation for our ideation.</p><h3>03 — From Ideas to Direction 💡</h3><p>After several rounds of ideation, our ideas started to converge.</p><p>It became clear to me:</p><blockquote><em>this wasn’t about adding features — <br> it was about staying one step ahead.</em></blockquote><p>An app that:</p><ul><li>understands your habits</li><li>anticipates disruptions</li><li>and adapts before problems impact your journey</li></ul><blockquote><em>A system that reduces uncertainty before it happens.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ojyj_8nqyVe8vAjOncAOEg.png" /></figure><h3>04 — Wireframing, Prototyping &amp; Testing 🖍</h3><p>In the low-fidelity phase, I focused on helping users make quick, confident decisions.</p><p>The challenge was balancing clarity and information without overwhelming the interface.</p><p>Testing showed that while the concept was strong, the navigation needed to be clearer.</p><blockquote><em>A good idea only works if users understand it instantly.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IruBaYsU4-TkO7wNhAY0Hg.png" /></figure><h3>05 — Final Concept 🎁</h3><p>The final concept aims to create a more <strong>predictable and supportive mobility experience</strong>.</p><p>Instead of forcing users to adapt to a complex system, the design adapts to them.</p><p>It learns how you move, understands your habits, and anticipates disruptions before they affect your journey.<br> Rather than reacting to problems, it helps you stay one step ahead of them.</p><p>The goal is not to add more features, but to <strong>reduce the mental load of commuting</strong>.</p><p>The focus is on:</p><ul><li><strong>clarity</strong></li><li><strong>simplicity</strong></li><li>and reducing uncertainty in everyday travel</li></ul><h3>06 — Reflection 💭</h3><p>This project changed the way I approach problem definition.</p><p>At first, I saw urban mobility as a problem of complexity — too many options, too many systems.<br> But through research, I realized it’s really about <strong>experience and perception</strong>.</p><p>What matters is not how many options exist, but how people understand, trust, and navigate them.</p><p>This project helped me:</p><ul><li>better <strong>understand the role of research</strong> in shaping design decisions</li><li>see how s<strong>mall frictions</strong> can have a <strong>big impact</strong> on daily experiences</li><li><strong>design for real behaviors,</strong> not ideal scenarios</li></ul><p>And honestly, the ideation phase is where I felt most in my element.<br> Exploring ideas freely — good, bad, unrealistic or unexpected — is where everything started to click for me.</p><h3>07 — Reflection on the team ⚽</h3><p>Working in a team pushed me to constantly adapt my role.</p><p>At different moments, I found myself <strong>listening, following, or pushing ideas forward.</strong><br> It wasn’t always clear at the beginning, and at times it felt like juggling multiple perspectives.</p><p>But over time, the dynamic became more <strong>natural.</strong><br> I learned how to balance my own ideas with the direction of the group, and how to contribute in a way that moves the team forward.</p><blockquote>We don’t move through cities with certainty — <br> we learn how to live with the uncertainty.</blockquote><p>Thanks for reading. ✌</p><p>I’d love to hear your thoughts.</p><p>Ivan.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59dec5280035" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>