EASY

Course Content
Part 1: User-centric Design
How can we design technology that truly works for the people using it? ☀️ In this part, we’ll explore what it means to put the user’s needs, context, and experience at the center of any design process. You’ll discover why successful products are rarely built from a “tech-first” mindset: they are crafted from understanding real human problems first. We’ll talk about empathy as a design tool, and how research methods such as interviews, observation, and usability testing help uncover what users actually want (and not just what they say they want). We’ll also explore how to translate user insights into design principles, prototypes, and iterative improvements. Why is this important? Because when users feel understood and supported by technology, they adopt it faster, use it longer, and trust it more. By the end of this section, you’ll know how to ask the right questions, analyze feedback, and turn those insights into designs that matter. 🌱
0/2
Part 2: Agile Thinking Introduction
In a world where technology changes overnight, sticking to a rigid, long-term plan can feel like trying to steer a ship through shifting icebergs. Agile thinking offers a different approach: one built on adaptability, flexibility, and steady forward movement. Instead of aiming for a “perfect” final product months down the line, Agile thinking encourages making small, continuous improvements that respond to real-time feedback. 🚲 In this part, you’ll learn how to break big goals into smaller, achievable steps, test your ideas early, and adapt based on what you discover. We’ll explore how Agile values: collaboration, transparency, and responding to change, can help you navigate both complex tech projects and everyday challenges. You’ll also see how Agile isn’t just for software developers: the same mindset can improve how you study, plan events, manage a personal project, or even handle unexpected changes in your daily routine. Why is this important? Because when you think in Agile terms, change stops feeling like a setback and starts becoming a tool. By the end of this section, you’ll be able to approach challenges with curiosity, adjust course quickly, and keep making progress... no matter what’s ahead. ⚡
0/2
Part 3: Agile Sprint Methodology
Once you have a clear vision and a flexible mindset, it’s time to bring it to life through structured collaboration. In this part, we’ll explore Agile sprints (short, focused work cycles) and the key ceremonies (or meetings) that keep teams aligned, motivated, and on track. You’ll learn how: daily stand-ups, sprint planning, reviews, and retrospectives -- each serve a specific purpose in improving both the product and the team’s way of working. We’ll discuss how to create a rhythm that balances discipline with creativity, making sure everyone knows what to do, when, and why. These ceremonies are not just about reporting progress: they’re about building trust, solving problems together, and continuously improving. Why is this important? Because Agile is not just a process; it’s a culture. By mastering these practices, you can create an environment where progress is steady, challenges are addressed early, and every team member feels invested in the outcome. 🌻
0/2
Module 8 – Technology Design and Programming

At the heart of great technology is one key principle: design for the people who will actually use it. User-Centric Design is a creative approach that starts with empathy: deeply understanding your users’ needs, goals, and challenges before building anything. 

This method follows a cycle:

  • research your users
  • define the problem from their perspective
  • brainstorm solutions
  • build simple prototypes, and 
  • test them with real people.

What makes it powerful is its focus on iteration: you improve based on feedback, rather than guessing what people want. In this part, we’ll explore how putting the user first can save time, reduce mistakes, and lead to products people actually love using.


Design Thinking
is more than a buzzword: it’s a mindset that begins and ends with people. In this module, we’ll focus on the first two stages of the method:
Empathy and Defining. Empathy means stepping into the shoes of the people you’re designing for, to truly understand their needs, frustrations, and desires. The Defining stage then turns those insights into a clear problem statement that guides your work. 

According to a recent five-year study by McKinsey & Company, companies that consistently followed design thinking practices generated roughly 32% more revenue and 56% higher returns for shareholders than those that did not.

These two stages form the foundation of the entire design process, followed by Ideation, Prototyping, and Testing (which you’ll explore in depth during Module 10). The last 3 stages are only as good as the clarity and human-centeredness of the early work. Skipping empathy or rushing the definition can lead to elegant solutions for the wrong problems.

Real-life example:

IDEO, a global design firm, once worked on improving hospital experiences for children. Instead of starting with technical fixes, the team shadowed young patients, noticed their anxiety in long corridors, and reframed the problem from “reduce waiting times” to “make waiting less frightening.” This led to playful, themed hallways that turned fear into curiosity. In tech, the same approach might turn “make an app faster” into “make it easier for new users to trust the app.”

Find out how AirBnb use designing thinking by reading the following article:

Article 🖱️


Our second tool,
User Personas, helps you capture and remember what you’ve learned about real people. A persona is a fictional but research-based profile that includes a name, photo, background, goals, challenges, and needs. Interviews are key here: even for beginners. 

Start simple: prepare 5–7 open-ended questions, listen more than you speak, and take note not only of what people say, but also how they say it. This combination of words, emotions, and context shapes a richer picture of the person you’re designing for. ❣️

User Persona Model

Empathy is not agreement; it’s accurate understanding, based on attentive listening skills. How might separating agreement-seeking from genuine understanding change the way you listen?

A well-framed problem is like a compass: it doesn’t tell you every step to take, but it keeps you moving in the right direction.

💡 What’s the smallest way you could make something more human-friendly today?
(note down in a journal)

Reflective exercise (1–2 min)
Think of a tool, website, or service you use daily. Write down one thing that frustrates you and one small change that would make it feel more personal, caring, or intuitive. 📝

Positive factors:
Taking regular, low-pressure opportunities to observe and talk to real users (even in restaurants, coffee shops, hallways, bus stations or other public spaces)
A work culture that values inquiry and accuracy in defining problems, before jumping to solutions.

Summary
In this first section, you explored how
user-centric design is the heart of technology that truly works for people. We introduced the first two stages of the Design Thinking process: Empathy — understanding users’ real needs, emotions, and challenges; and Defining — turning those insights into a clear, human-centered problem statement. You learned that skipping these early steps can result in beautifully built solutions… to the wrong problems! 🏗️

Through real-life examples from IDEO, you saw how shifting perspective can redefine the challenge itself. For example, improving a child’s hospital stay wasn’t just about speed; it was about making the waiting experience less frightening. This same mindset applies to tech design: sometimes the deeper need is trust, clarity, or joy, not just efficiency. ⚠️

We also explored User Personas as a practical tool to keep real people at the center of your work. You discovered how simple, structured interviews can provide valuable insights, even if you’re just starting out. Listening actively, observing small details, and capturing them in a persona profile helps keep your design anchored in reality.

Key takeaways:

  • Empathy is about accurate understanding, not necessarily agreement.
  • A well-defined problem acts like a compass for creative solutions.
  • Small changes can make products and services feel more human.
  • Personas and interviews make abstract “users” feel real and specific.

You practiced quick reflection on how to make everyday tools more personal, and learned two systemic factors that enable this mindset: small daily opportunities to talk to real users, and cultures that favour curiosity before solutions.

Progress forward: Congratulations for completing Part 1! ✅ You’ve built the foundation for designing with people in mind. Next, we move to Agile Thinking: learning how to adapt quickly, make small improvements, and keep moving forward without waiting for “perfect.”

Gérer le consentement aux cookies

Afin d'offrir la meilleure expérience possible, nous utilisons des technologies telles que les cookies pour stocker et/ou accéder aux informations des appareils. Le fait de ne pas consentir ou de retirer son consentement peut avoir un effet négatif sur certaines caractéristiques et fonctions.

View more
Cookies settings
Accepter
Refuser
Confidentialité et cookies
Privacy & Cookies policy
Cookie name Active
Save settings
Cookies settings