1‑on‑1 Chat: Weeks 5-6 (covers Weeks 3–4)#
What this is (15 min):
A short check‑in to see how things are going now that you’ve started doing real project work. We’ll talk about customer interviews, early teamwork habits, and your first experiences with GitHub.
What this isn’t:
Not a test
Not a technical exam
It’s normal to feel…
Awkward approaching strangers, unsure about Git, or like your team is still figuring things out. That’s exactly where most students are at this point.
Structure (how we’ll use the 15 minutes)#
0–5 min: Check‑in. How are you going overall? What’s felt confusing or uncomfortable?
5–10 min: Customer discovery. What you learned from talking to people.
10–15 min: Tech & teamwork. Git, Markdown, and how meetings are running.
How to prepare#
You don’t need to revise.
Skim your customer interview notes.
Remind yourself of the difference between open and closed questions.
Make sure you know where your team’s GitHub repo lives (even if you’re still unsure how everything works).
Topics to Think About (Weeks 3–4)#
Customer Interviews: Open vs Closed Questions
What differences did you notice in the answers you got?
What felt uncomfortable about approaching strangers?
What did you learn from reading the transcripts afterward?
Running Effective Meetings
Has your team held a proper meeting yet?
Did you use an agenda and start on time?
Who is tracking notes and action items (“who does what by when”)?
Repositories, Git, and Markdown
Why is emailing code a Very Bad Idea for teams?
Have you cloned the repo and pushed at least one Markdown file?
How did your team handle the fake merge conflict exercise?
Action plan#
Leave the chat with one small, clear next step for the next fortnight
(e.g. rewrite interview questions to be more open, run the next meeting with an agenda, make one clean Git commit).