The Final Chapter

 

HCI Blog 6 – The Final Chapter:



If Blog 1 was called A Beginning, then this one feels like A Becoming.
Somewhere between the paper prototypes, the late-night Figma edits, the interviews with sleepy commuters, and the endless “HMW” questions, something shifted in me. It’s funny—HCI wasn’t just a class; it became a mirror, a map, and sometimes a punch in the stomach reminding me, “Design is not about you. It’s about them.”

This final reflection is not an essay.
It’s a letter to the version of me who walked into this course on the first day, half-curious, half-confident, and completely unaware of how much this journey would change him.

Dear Rustam (from 3 months ago),

You had no idea what you were walking into.

You thought HCI was going to be “another design course.”
You thought UX decisions were mostly about aesthetics.
You thought you already knew how users think because you are a user.

You were wrong—and that’s what made this course so important.

There will be moments in this class when you feel lost, moments where the workload feels like a wave crashing over you, and moments where everything clicks and you say, “Wait… why does this actually feel fun?”

You will meet people—drivers, homeowners, commuters—who trust you enough to share their frustrations for your research. You’ll listen to them talk about safety, money, time, and stress. And suddenly your project won’t just be a project.
It will become a responsibility.

That is when you’ll start designing like a human being, not just a programmer.

The Rollercoaster Ride

Some parts of this journey were exhilarating—like seeing our low-fi sketches evolve into a living prototype, or watching people interact with our designs and say, “Oh, this actually makes sense.”

Some parts were… painful.

Affinity diagramming felt like drowning in sticky notes.
Running interviews felt like balancing research and psychology.
And iteration?
Iteration felt like tearing down things I liked just because the user didn’t.

But this rollercoaster had a purpose. Every high and low added depth to the final design. Every frustration became a feature. Every mistake became an insight.

DriveShare: My Favorite Kind of Chaos

Building DriveShare, a peer-to-peer driveway rental platform, was the heart of my HCI learning.
Our research taught me that the problem wasn’t “cheap parking”—it was time, safety, and reliability.

Users didn’t want the cheapest spot. They wanted:

  • a guaranteed reservation

  • safety indicators

  • trust between renter and homeowner

  • flexibility

  • clear pricing

  • simple navigation

And suddenly, our project became more than a parking app.
It became an exercise in understanding people—not ideal users, not personas, but real humans who were tired, stressed, late, anxious, and hopeful.

That shift was the moment I became a designer instead of a developer.

What I Learned About Myself



If I could summarize my growth in one sentence:

HCI taught me to slow down, listen deeply, and design with humility rather than ego.

I learned that:

  • Good design starts with empathy, not assumptions.

  • A prototype is a living organism—it grows, evolves, and sheds its skin.

  • User research is not optional; it is the backbone of every meaningful decision.

  • Trust is the real currency of design. Features are just the packaging.

And maybe the biggest surprise…
I genuinely enjoyed this process.
I enjoyed being wrong, getting feedback, and rebuilding things better.

What I Wish I Knew Before

If I could send advice backward in time, I’d tell myself three things:

  1. You won’t design well until you stop designing for yourself.

  2. Users don’t always know what they want, but they absolutely know what frustrates them.

  3. Your first idea is never your best idea. Your 7th idea might be. Your 11th might actually work.

A Letter to Future HCI Students

To whoever is about to take this class:

You are going to build something you’ve never built before.
You are going to fail, a lot.
You are going to redesign things you thought were perfect.
You are going to get feedback that stings.
And you are going to produce work you’re genuinely proud of.

Here is my advice:

  • Talk to your users. Really talk to them.

  • Don’t fall in love with your first prototype. Fall in love with the problem.

  • Iterate like your grade depends on it—because it does.

  • Design for humans first. Technology comes second.

  • Have fun. Seriously. Make it playful.

This course rewards the students who stay curious, humble, and willing to experiment.

How HCI Will Shape My Future

As someone pursuing AI research and product development, HCI has become the missing piece in my toolkit.
I now see every future project—AI agents, apps, tools, research projects—as something that must serve real humans, not abstract metrics.

I don’t just want to build powerful technology.
I want to build technology that feels empowering.
Technology that understands frustration.
Technology that respects the user.
Technology that earns trust.

DriveShare may be a class project, but its design challenges mirror real-world problems, and the lessons I’ve learned will guide every startup idea, research prototype, and AI product I build from now on.

Final Thoughts: The Magic of HCI

If HCI has a magic, it’s this:

It brings compassion into technology.
It forces you to see beyond the screen and into the person holding it.
It turns design into a language of care, clarity, and respect.

This class didn’t just teach me how to design better.
It taught me how to see better.

And for that, I’m grateful.

Comments

Post a Comment

Popular posts from this blog

From Medium-Fidelity to a Polished Hi-Fidelity Prototype

Image
  HCI Blog 5 Building the hi-fidelity prototype for DriveShare felt like the moment where everything finally came together—our user research, the medium-fidelity sketches, and all the messy feedback we collected in between. This stage wasn’t just about making the app look better; it was about understanding what makes an interface trustworthy, intuitive, and good enough for real people to use. Using Nielsen’s 10 Usability Heuristics as my guide, this was the first time I felt like a real product designer—someone who listens, iterates, and reshapes a design based on evidence, not assumptions. This blog reflects on how I evaluated the medium-fidelity design, the usability flaws we uncovered, and how the DriveShare experience transformed into a cleaner, more reliable prototype. It also touches on what this taught me about UX, and how these lessons shape my future as an AI product engineer. 1. Evaluating the UI with Nielsen’s Heuristic Evaluation To evaluate our medium-fidelity pr...
Read more

Bringing Ideas to Life

Image
  Introduction In my previous blog, I reflected on how user research helped my team rethink our direction and move from an AR Cooking Assistant to a more practical, everyday concept: DriveShare —a peer-to-peer parking app that allows homeowners to rent out their driveways to drivers looking for affordable, reliable parking. This blog is about the creative process that followed—how our team transformed research findings into a visual story through brainstorming, design planning, and finally, our DriveShare concept video . The journey taught me that bringing an idea to life isn’t only about visuals or technology—it’s about empathy, storytelling, and making the design feel real. From Idea to Solution: Shaping the Concept After completing our user interviews, we discovered that trust and safety mattered as much as cost. That finding shifted how we defined DriveShare’s core purpose: not just to make parking cheaper, but to make it predictable and secure for both drivers and homeo...
Read more