emalyn.

Speaking framework

PCS — the framework for
analytical thinking questions

PCS stands for Problem, Cause, Solution. It's the clearest way to answer any question about how you think through a challenge — identifying what went wrong, why it happened, and what you did about it. One structure. Logical. Impossible to ramble with.

P Problem "Define the issue clearly" Describe the problem in one or two sentences. What was wrong and what was the impact? Be specific — vague problems lead to vague answers.
C Cause "Why it happened — root cause" Go one level deeper than the obvious. Explain the underlying reason, not just the symptom. This is where your analytical thinking shows.
S Solution "What you did or would do" Explain your specific actions and the result. Include what changed or what you'd do differently. Your solution only makes sense once the cause is clear.
"How did you handle..." Case study questions Analytical interviews Process improvement Problem-solving discussions Root cause analysis

"Most people jump straight to the solution. That's the wrong order. The Cause is what separates a thoughtful answer from a shallow one. Define the problem, find the root cause — then your solution sounds inevitable, not lucky."

PCS
Daily life examples

4 situations where PCS works

Click each one to see the full structure and a model answer.

Example 01 · Teaching / Work Explaining how you solved a recurring problem at work "Tell me about a problem you identified and fixed in your workplace."
❝ Tell me about a problem you identified and fixed in your workplace. ❞
Problem
Define the issue clearly My students were consistently failing their oral assessments — not because they didn't know the answers, but because they froze the moment they had to speak. Scores were low, confidence was lower, and the same students were repeating this pattern every term.
Cause
Why it actually happened The root cause wasn't vocabulary or grammar — they had enough of both. The real issue was that they had almost no structured speaking practice between lessons. They were being tested on a skill they never got to rehearse. That gap was the actual problem.
Solution
What you specifically did I built a free speaking drill tool — scenario cards with a timer and a speaking framework on each card. Students could practise alone, any time, with no pressure. Within one term, participation jumped and oral assessment scores improved across the board.
Full answer — read it out loud

My students were consistently failing oral assessments — not because they lacked knowledge, but because they froze when they had to speak. Low scores, low confidence, same pattern every term. The root cause wasn't vocabulary or grammar — it was that they had almost no structured speaking practice between lessons. They were being tested on a skill they never got to rehearse. I built a free speaking drill tool — scenario cards with a timer and a framework on each. Students could practise alone, any time, no pressure. Within one term, oral scores improved across the board.

Example 02 · Process / Efficiency Answering a process improvement interview question "Describe a time you improved a process or system at work."
❝ Describe a time you improved a process or system at work. ❞
Problem
Define the issue clearly Our team was spending the first 20 minutes of every Monday meeting going over updates that everyone already had access to. It was slow, frustrating, and by the time we reached actual decisions, people were already disengaged.
Cause
Why it actually happened We had no shared system for updates before the meeting. Everyone showed up without a common baseline, so the meeting became the place information was distributed rather than discussed. The format was designed for a team that shared nothing between sessions.
Solution
What you specifically did I introduced a simple weekly update doc — five bullet points per person, shared every Friday afternoon. By Monday the whole team had context. Meetings dropped from 90 minutes to under an hour, and we used the time for actual decisions.
Full answer — read it out loud

Our team spent the first 20 minutes of every Monday going over updates everyone already had. By the time we reached decisions, people were disengaged. The cause was that we had no shared system before the meeting. Everyone arrived without a common baseline, so the meeting became the place information was distributed rather than discussed. I introduced a simple weekly update doc — five bullets per person, shared every Friday. Meetings dropped from 90 minutes to under an hour and became genuinely productive.

Example 03 · Personal Talking about a personal challenge you worked through "How did you handle moving to a new country where you didn't know anyone?"
❝ How did you handle moving to a new country where you didn't know anyone? ❞
Problem
Define the issue clearly When I moved to Bangkok from the Philippines, I had no network, no friends, and no support system. The isolation was real — I'd finish work, come home, and have no one to talk to. After a few weeks it started affecting my energy and focus.
Cause
Why it actually happened The core cause was that I was waiting for connections to happen naturally — the way they do in a familiar environment. But abroad, that passive approach doesn't work. In a new country you have to actively create the conditions for connection. I hadn't done that yet.
Solution
What you specifically did I set a personal rule — say yes to every social invitation for three months. I also started a free online English conversation club on Zoom, which let me meet people through something I was already good at. Within a few months I had a real community and Bangkok became home.
Full answer — read it out loud

When I moved to Bangkok I had no network at all. The isolation was real — after a few weeks it started affecting my energy and focus at work. The core cause was that I was waiting for connections to happen naturally, the way they do in familiar environments. Abroad, that passive approach doesn't work. I hadn't actively created the conditions for connection. I set a rule — say yes to every social invitation for three months. I also started a free online English conversation club on Zoom to meet people through something I was already confident at. Bangkok became home.

Example 04 · Analytical / Hypothetical Answering a hypothetical problem-solving question "If student engagement in your class suddenly dropped, how would you approach it?"
❝ If student engagement in your class suddenly dropped, how would you approach it? ❞
Problem
Define the issue clearly first I'd start by defining what "dropped" actually means — is it participation, homework completion, test scores, or just the energy in the room? Engagement is broad. The right fix depends on which specific behaviour changed and by how much.
Cause
Find the root cause before acting Then I'd look for the underlying cause. Is the content too difficult or too easy? Did something change in the class dynamic — a new student, a conflict, a scheduling issue? I'd talk to a few students informally and observe patterns before drawing any conclusion.
Solution
Match the solution to the cause Once I understood the cause, I'd target the solution to match it exactly. Content too passive? Add interactive activities. Confidence issue? Reduce pressure, create low-stakes moments. The solution only makes sense after you understand the cause — that's why I wouldn't act on the first guess.
Full answer — read it out loud

First I'd define what "dropped" means — participation, homework, scores, or just the energy in the room. Engagement is broad, and the right fix depends on which specific behaviour changed. Then I'd look for the root cause before acting. Is the content the wrong level? Did something change in the class dynamic? I'd talk to a few students informally and observe patterns before drawing a conclusion. Once I understood the cause, I'd match the solution to it. Content too passive — add interactive activities. Confidence issue — reduce pressure, create low-stakes moments. The solution only makes sense after you understand the cause.

3 things to remember when using PCS

01 The Cause is the most important part

Anyone can describe a problem. Anyone can name a solution. What separates a strong answer from a weak one is the Cause — showing you understand why something happened. This is where analytical thinking lives. Spend more time here than anywhere else.

02 Go one level deeper on the cause

"The system was broken" is not a cause — it's a symptom. Ask yourself: why was it broken? Who or what created the conditions for it to fail? The real cause is usually one step behind what's obvious. When you find it, your solution automatically sounds more credible.

03 PCS works for hypothetical questions too

"What would you do if..." questions are answered brilliantly with PCS. Define the problem clearly first, explain what you'd investigate as the cause, then describe your solution approach. It shows structured thinking — exactly what analytical questions are testing for.

What goes in each part

Problem

What was wrong — defined clearly

Name the issue specifically. Include the impact — what was affected and how badly. One or two sentences is enough.

Students failing oral assessments every term Meetings running 30 minutes over time Customer complaints increased by 40% Team morale visibly and consistently low
Cause

Why it happened — root level

Go deeper than the obvious. Explain the underlying reason, not just the symptom. This is where your thinking shows.

No structured practice between lessons No shared baseline before meetings Unclear ownership of the process Waiting passively instead of acting
Solution

What you did — specific and with results

Describe your exact actions. Include what changed as a result. Numbers and outcomes make your solution sound real, not theoretical.

Built a free speaking drill tool Introduced a Friday update document Created clear process ownership matrix Set a "say yes" rule for three months

Now practise PCS
out loud.

Pick a real problem you've solved and walk through it using PCS. Aim for 90 seconds.

Open Daily Drill →