Design Thinking
for Civil Engineers
Learn to understand people, frame the right problem, generate better ideas, build prototypes and learn through testing.
๐ฏ Course Learning Outcomes
By the end of the course, students move from an ambiguous real-world need to a tested design concept.
CO1 · Understand
Explain Design Thinking principles, mindset and process.
CO2 · Empathize
Apply interviews, observation, shadowing and empathy mapping.
CO3 · Define
Develop POV statements and How Might We questions.
CO4 · Ideate
Generate, evaluate and select innovative alternatives.
CO5 · Prototype
Create low/high-fidelity physical or digital prototypes.
CO6 · Iterate
Test, learn and improve using user evidence.
Unit I · Introduction to Design Thinking
Think like a designer before you solve like an engineer.
Definition · History · Mindset · Five-Step Process
Human-centered problem solving and the evolution of Design Thinking.
๐ Lecture Notes
Design Thinking is an iterative, human-centered approach to understanding needs, framing opportunities, generating possibilities, building representations and learning through testing.
Core principles
- Empathy and human-centeredness
- Collaboration
- Divergent and convergent thinking
- Experimentation
- Iteration and learning from failure
๐ Detailed Lecture Notes · Unit I
1. What is Design Thinking?
Design Thinking is a human-centred, iterative approach to solving problems and creating useful, desirable and feasible solutions. It begins with understanding people and their context rather than assuming that the problem is already perfectly defined.
For a Civil Engineering student, Design Thinking means combining engineering knowledge with an understanding of people, places, behaviour, safety, accessibility, cost, sustainability and the environment.
2. Why is Design Thinking needed?
- Many engineering problems are “wicked” or ambiguous rather than completely defined.
- Technical correctness alone does not guarantee user acceptance.
- Users often adapt to poor facilities through workarounds that engineers may not notice.
- Early prototypes allow assumptions to be tested before expensive implementation.
- Collaborative ideation produces alternatives that may not emerge from routine analysis.
3. History and Evolution
Design Thinking has roots in design practice, engineering design, creativity research and human-computer interaction. In contemporary practice, it became strongly associated with human-centred innovation and was popularised in business and social innovation through organisations such as IDEO and the Stanford d.school.
The modern approach therefore connects design, technology, business and human needs. It is not simply a five-step recipe; the stages are revisited as new evidence is discovered.
4. Design Thinking Mindset
Empathy
Understand people's experiences rather than designing from assumptions.
Curiosity
Ask “why?”, “what if?” and “what else?” before deciding.
Experimentation
Build small experiments to learn quickly.
Collaboration
Combine perspectives of users, engineers and stakeholders.
Iteration
Improve the idea repeatedly using evidence.
Learning from failure
Treat unsuccessful tests as useful information.
5. Design Thinking vs Traditional Problem Solving
| Traditional approach | Design Thinking approach |
|---|---|
| Problem is often assumed to be known. | Problem is investigated and reframed. |
| Focuses strongly on analysis and optimisation. | Balances analysis with human experience and experimentation. |
| Often moves toward one preferred solution. | Generates several alternatives before selecting. |
| Testing may happen late. | Testing and feedback occur early and repeatedly. |
| Failure is often avoided. | Small, controlled failures are used for learning. |
6. The Five-Step Process
Empathize: Understand users, stakeholders, context, behaviour and needs.
Define: Synthesise evidence and frame a focused problem.
Ideate: Generate a wide range of possible solutions.
Prototype: Make an idea tangible at an appropriate level of detail.
Test: Put the prototype in front of users, observe, collect feedback and learn.
7. Civil Engineering Example
Challenge: Students complain that a campus pathway becomes difficult to use during rain.
Wrong starting point: “Construct a bigger drain.”
Design Thinking starting point: Who struggles? Where does water accumulate? How do students currently cope? Are pedestrians, maintenance staff and security affected differently?
The eventual solution could involve drainage, surface slope, pedestrian routing, covered walkways, maintenance practices or a combination. The point is to discover the right opportunity before committing to a solution.
8. When to Use Design Thinking
- When user needs are unclear.
- When several solutions are possible.
- When stakeholder expectations conflict.
- When existing solutions are technically adequate but poorly used.
- When innovation, accessibility or user experience matters.
9. Key Takeaway
๐ PPT · ๐ฅ Video · ๐ Notes
Replace these placeholders with your institutional resources.
๐งช Lab Experiment · Design Thinking Mindset
- Write the initial problem statement.
- Identify three user groups.
- List assumptions.
- Reframe the problem from the user's perspective.
- Produce three alternative interpretations.
Unit II · Empathize – Understanding Users
Understand users before designing for them.
User Research · Interviews · Observation · Shadowing · Empathy Mapping
Discover real user behavior, pain points and needs.
๐ Lecture Notes
Interview
Use open-ended questions about actual experiences, frustrations and workarounds.
Observation
Watch movement, waiting, errors, repeated behavior and environmental constraints.
Shadowing
Follow a user through an activity to understand the complete journey.
Empathy Map
SAYS · THINKS · DOES · FEELS → identify PAINS · NEEDS · GAINS · INSIGHTS.
๐ Detailed Lecture Notes · Unit II
1. Meaning of Empathy in Design
Empathy means making a deliberate effort to understand a user's experiences, feelings, goals, constraints and behaviour from the user's point of view. In Design Thinking, empathy is evidence gathering—not guessing what users want.
2. Why Empathy Matters in Civil Engineering
- A facility can satisfy a code or calculation and still be difficult for people to use.
- Different users experience the same space differently.
- Children, elderly people, persons with disabilities, workers and visitors may have different needs.
- Observation can reveal problems that users do not explicitly report.
- Understanding maintenance staff can expose operational constraints missed during design.
3. User Research Methods
Interview
A conversation used to learn about experiences, motivations, difficulties and expectations.
Use when: you need the user's story, reasoning or perception.
Observation
Systematically watch what people actually do in a real setting.
Use when: behaviour may differ from what people say.
Shadowing
Follow a user through a task or journey to understand sequence, interruptions and workarounds.
Use when: the activity unfolds over time.
4. Interviewing: Good Practice
- Start with easy questions and build trust.
- Ask open-ended questions: “Tell me about the last time…”
- Ask “Why?” and “What happened next?” without interrogating.
- Avoid leading questions such as “You find this inconvenient, don't you?”
- Ask about actual recent behaviour rather than hypothetical wishes alone.
- Record observations and quotations accurately.
- Obtain appropriate consent before recording or photographing people.
5. Observation: What Should a Civil Engineer Notice?
Observe movement, waiting, queues, access, errors, safety behaviour, weather effects, workarounds, signage, maintenance, cleanliness, accessibility and interaction with the physical environment.
Example: At a staircase, do not only count steps. Observe where people stop, whether handrails are used, whether water accumulates, whether users avoid the staircase and why.
6. Shadowing
Shadowing follows a person through a complete activity. For example, follow a maintenance worker during a routine inspection. Record tools used, distances walked, repeated actions, delays, safety risks and information required.
7. Empathy Map
SAYS
What does the user explicitly say?
THINKS
What concerns or priorities may influence decisions?
DOES
What behaviour is actually observed?
FEELS
What emotions or frustrations appear?
After mapping these four areas, identify Pains, Needs, Gains and useful Insights.
8. Pain Point vs Need vs Solution
| Category | Example |
|---|---|
| Pain point | Students wait in a long queue for drinking water. |
| Need | Students need convenient access to drinking water with less waiting. |
| Solution | Add another water dispenser. |
Important: A solution should not be mistaken for a need. During Unit II, remain curious about the underlying need.
9. Exercise: Empathize with a Campus User
- Select one facility: toilet, footpath, bus stop, water point, staircase, parking or drainage.
- Identify at least three user groups.
- Prepare 6–8 open-ended interview questions.
- Interview 5–8 users where appropriate.
- Observe the facility for 20–30 minutes.
- Create an empathy map.
- List five pain points and five needs.
- Write three evidence-based insights.
10. Ethics and Quality of Research
Respect privacy, obtain consent when required, avoid collecting unnecessary personal information and never fabricate observations. Separate what you observed from what you inferred.
11. Key Takeaway
๐ฅ Recommended YouTube Learning · Units I & II
Because individual YouTube videos can change or become unavailable, the buttons below use YouTube topic searches rather than hard-coded video IDs.
๐ Field Research Guide
- Interview 5–8 representative users.
- Observe for 20–30 minutes.
- Ask neutral, open-ended questions.
- Record exact observations.
- Create an empathy map.
๐งช Lab Experiment · Empathy Field Study
- Identify users and stakeholders.
- Conduct 5–8 interviews.
- Observe for 20–30 minutes.
- Prepare empathy map.
- Identify at least five pain points and five needs.
- Record three unexpected observations.
Unit III · Define – Framing the Problem
Turn scattered observations into a focused design challenge.
Research Synthesis · POV · Opportunity Framing · HMW
Observations → Patterns → Insights → Needs → Challenge.
๐ Lecture Notes
Affinity Mapping
Cluster similar observations to discover patterns without jumping directly to solutions.
POV Statement
[User] needs [need] because [insight].
HMW Question
How might we + action + user + desired outcome?
๐งช Lab Experiment · Problem Framing Workshop
- Create affinity clusters.
- Identify patterns and insights.
- Identify user needs.
- Write a POV statement.
- Generate five HMW questions.
- Select the strongest design challenge.
Unit IV · Ideate – Generating Ideas
Expand the solution space before narrowing it.
Brainstorming · Storyboarding · Sketching · Lateral Thinking
Divergent/convergent thinking and Edward de Bono techniques.
๐ Lecture Notes
Crazy 8s
Generate eight concepts rapidly.
Brainwriting
Generate independently, then build on others' ideas.
SCAMPER
Substitute · Combine · Adapt · Modify · Put to use · Eliminate · Reverse.
Worst Idea
Make the problem worse, then reverse the insight.
Random Entry example: “Umbrella” for drainage → protection, collection, deflection, distributed coverage.
๐งช Lab Experiment · Idea Generation Studio
- Generate 20 conventional ideas.
- Complete Crazy 8s.
- Apply SCAMPER.
- Apply Random Entry and Provocation.
- Extract a concept from another system.
- Use a selection matrix: user value, feasibility, sustainability, innovation and cost.
Unit V · Prototype & Test
Make ideas tangible, test assumptions and improve.
Prototyping · Think-Aloud · A/B Testing · Iteration
Low/high fidelity · physical/digital · reflection loops.
๐ Lecture Notes
Low Fidelity
Paper, cardboard, clay, foam, sketches and rough mock-ups.
High Fidelity
Detailed CAD/3D models, functional prototypes and interactive interfaces.
Think-Aloud
User performs a task while verbalizing thoughts.
A/B Testing
Compare two alternatives using preference or behavior evidence.
Prototype → Test → Learn → Modify → Retest
๐งช Lab Experiment · Prototype & Test
- Identify the riskiest assumptions.
- Build Prototype V1.
- Prepare a test protocol.
- Conduct user testing.
- Document failures and feedback.
- Build Prototype V2.
- Compare V1 and V2.
๐งช Laboratory Studio
Five unit-wise experiments build the skills required for the final project portfolio.
01 · Mindset
Reframe a campus problem from the user's perspective.
02 · Empathize
Interview, observe and map users.
03 · Define
Create affinity maps, POV and HMW.
04 · Ideate
Use brainstorming and lateral thinking.
05 · Prototype/Test
Build, test, learn and iterate.
๐️ Five Real-World Civil Engineering Projects
Students complete the full Design Thinking cycle for each challenge.
Project 01 · Campus Movement
How might we make movement around campus safer and more convenient?
Project 02 · Water Management
How might we reduce inconvenience caused by rainwater accumulation?
Project 03 · Waste Management
How might we improve waste segregation among students?
Project 04 · Construction Safety
How might we improve safety awareness and behavior?
Project 05 · Inclusive Facility
How might we make a toilet, bus stop, footpath or classroom more inclusive?
๐ Assessment Framework
| Component | Marks | Evidence |
|---|---|---|
| Design Thinking concepts | 10 | Quizzes / concept checks |
| Empathy research | 15 | Interviews, observations, empathy map |
| Problem definition | 15 | Affinity map, POV, HMW |
| Ideation | 15 | Idea volume and diversity |
| Prototype | 15 | Appropriate prototype |
| Testing & iteration | 15 | User evidence + V1/V2 |
| Final report | 10 | Project portfolio |
| Reflection | 5 | Learning and changed assumptions |
๐ง Unit-wise MCQ Quiz
Minimum 5 questions for every unit. Select an answer and click Check Answer for instant feedback.
Quiz Instructions
- Each unit contains 5 MCQs.
- Attempt the questions after completing the corresponding lecture and lab.
- Use the feedback to identify concepts that need revision.
- For a formal assessment, your instructor can convert these into a scored Google Form or LMS quiz.
๐ Quiz Progress
Attempted: 0 / 25 · Correct: 0

No comments:
Post a Comment