Explain brick and timber of communication in plain English, why interviewers ask it, and how to answer in 20 to 30 seconds without sounding scripted.
You've heard the phrase once, maybe in a job description or a mock interview, and now it's sitting in your brain like a splinter. The brick and timber of communication is one of those expressions that sounds like it should be obvious — and yet, when someone asks you to explain it on the spot, the words dissolve. The problem isn't that you don't communicate well. It's that you've never been handed a plain-English definition that actually holds up under a follow-up question.
This guide fixes that. It explains what the phrase means, why interviewers reach for it, and how to give a 20- to 30-second answer that sounds like a person talking — not a candidate reciting. If you're a coach or hiring manager, there's guidance here for you too, but the frame is the candidate's experience first, because that's where the gap is widest.
What Brick and Timber of Communication Means in Plain English
Stop treating it like a mysterious phrase
The metaphor is simpler than it sounds. In construction, bricks and timber are the raw structural materials — the things that hold a building up and give it shape before any of the finishing work happens. Applied to communication, the phrase points to the same idea: every clear message has two foundational materials working together. The timber is the structure — the logical frame that tells the listener where you're going and why. The brick is the substance — the specific evidence, detail, or example that makes the message believable and load-bearing.
Neither material works alone. Timber without brick is a frame with no walls — you can see the shape of an argument but there's nothing solid to stand on. Brick without timber is a pile of material on the ground — dense, possibly impressive, but not organized into anything useful. The phrase is really about the relationship between those two things: a clear point, supported by real proof.
It's worth being honest here: the phrase doesn't have a single verified origin in communication theory. If someone tells you it comes from a specific book or framework, treat that claim skeptically unless they can point to a primary source. What matters for your purposes is the functional meaning — and that meaning is consistent across the contexts where it shows up.
What this looks like in practice
Imagine you're giving a project update in a team meeting. A weak version sounds like this: "Things are progressing well, we've had some challenges but the team is working hard and we're staying on track." That's all timber and no brick — there's a shape to it, but nothing load-bearing.
A version that uses both materials sounds like this: "We're on schedule for Friday's launch. We hit a blocker on Tuesday when the API integration broke, but the dev team patched it in four hours and we're back on track." Same message, but now there's a specific event, a specific resolution, and a specific timeline. The listener can trust it.
A communication coach or experienced hiring manager will often say that when they hear this phrase used correctly in an interview, it signals something specific: the candidate has learned to distinguish between having a point and making a point. Those are different skills, and most people conflate them until someone forces the distinction.
Why Interviewers Care About Brick and Timber of Communication
They're not testing vocabulary, they're testing clarity
When an interviewer asks about communication structure — whether they use this phrase or something adjacent — they're not running a vocabulary quiz. They're watching how you handle a question that requires you to organize a thought in real time, under mild pressure, about an abstract concept. That's almost exactly what you'll do in the job when you explain a decision to a skeptical stakeholder, brief a manager on a project that's gone sideways, or walk a client through something complicated without losing them.
The research on this is consistent. According to Harvard Business Review, clear communication is one of the most frequently cited differentiators between employees who get promoted and those who plateau — not because the high performers know more, but because they can explain what they know in a way that earns trust. The brick-and-timber framing is a shorthand for exactly that skill.
What this looks like in practice
Consider a candidate asked to explain a missed deadline. A structurally weak answer spends 45 seconds on context, mentions several contributing factors without prioritizing any of them, and ends with something like "but we learned a lot from it." It's not dishonest — it's just not organized. The interviewer walks away unsure what actually happened or whether the candidate understands it.
A structurally strong answer does three things quickly: it names the outcome ("we missed by three days"), names the cause ("a dependency we hadn't scoped correctly"), and names what changed as a result ("we now add a dependency audit to every kickoff"). That's it. The listener has a complete picture in under 30 seconds, and the candidate sounds like someone who can be trusted to communicate under pressure.
One hiring manager who screens for senior individual contributors put it this way: "I'm not looking for polish. I'm looking for whether the person can give me the useful sentence. A lot of candidates give me five sentences when one would have done it — and that tells me something about how they'll run a meeting."
Give the 20- to 30-Second Answer You Can Say Without Sounding Rehearsed
The answer should sound like a person, not a script
The interview answer framework you need here has three parts, and they should take about 20 to 30 seconds total. Part one: a plain-English definition in your own words. Part two: one concrete example from a real work context. Part three: one sentence on why it matters — not in the abstract, but in a job like the one you're applying for.
The warning that matters most: over-polishing kills the natural tone. If you memorize a definition word-for-word, the interviewer will hear it. The goal isn't to recite the metaphor back to them — it's to demonstrate that you actually understand it by showing it in action. The example does more work than the definition.
What this looks like in practice
Here's a sample answer that lands in under 30 seconds, set in a common work context:
"To me, it's the idea that good communication needs two things working together — a clear structure so the listener knows where you're going, and specific detail that makes the message believable. Like if I'm updating my manager on a project, I don't just say 'it's going well.' I'd say 'we're on track for Thursday, we had a blocker on the integration but it's resolved.' The structure is the update. The specific detail is what makes it worth trusting."
That answer is 70 words. It defines the concept, uses a real scenario, and closes with a sentence that shows the candidate understands the why. A communication coach or recruiter reviewing this structure would note that the example is doing the heavy lifting — it's not abstract, it's not borrowed from a textbook, and it sounds like something the candidate has actually done.
According to the SHRM guidelines on behavioral interviewing, answers that use specific, observable examples are rated more credible by interviewers than answers that rely on general claims — even when the general claims are accurate. The example is the brick. Don't skip it.
Personalize the Answer Without Making It Sound Memorized
The trick is to swap in your own work example
Speaking clearly in interviews gets harder when you're trying to use someone else's example. The structure above is a scaffold — the part that belongs to you is the work scenario you drop into it. You don't need to rebuild the whole answer. You need to find one moment from your own experience where you communicated something clearly under pressure, and use that moment as your brick.
The structure stays the same: what the concept means, one example, why it matters. What changes is the example. That swap is what makes the answer yours.
What this looks like in practice
Here's how the same framework adapts across two different roles:
Project manager version: "For me, it's about combining structure with specifics. When I present a status update, I don't just say things are on track — I'll say 'we delivered milestone two on Tuesday, and milestone three is scoped and assigned, due Friday.' The structure is the update format. The specifics are what make it credible."
Developer or analyst version: "I think of it as the difference between explaining what I built and explaining why it matters. I might say 'I refactored the data pipeline — it was running in 40 minutes, now it runs in 8.' The structure is the before-and-after. The specific number is what makes it land."
A coach who works with candidates on interview readiness will often observe that personalization fails not because the candidate chose the wrong example, but because they grafted a template example onto their own experience without adjusting the language. The language has to match the role. A developer who says "I updated my stakeholders on deliverables" sounds like they're borrowing a project manager's script. Use the vocabulary of your actual job.
Show the Weak Answer and the Strong One Side by Side
The weak answer sounds busy but says almost nothing
The vague, high-energy answer has a logic to it. It feels safe because it doesn't commit to anything specific that could be challenged. A candidate who says "I'm a strong communicator — I always make sure my team is aligned and I adapt my style to my audience" hasn't said anything wrong. They've just said nothing useful. The answer has the shape of a communication skills example without the substance of one.
The problem is that interviewers have heard this answer hundreds of times, and they've learned that it predicts nothing. It doesn't tell them how the candidate behaves when communication breaks down, when the message is complicated, or when the audience is skeptical.
What this looks like in practice
Weak answer: "Communication is really important to me. I always try to be clear and make sure everyone is on the same page. I adapt my style depending on who I'm talking to, whether it's technical or non-technical. I think good communication is the foundation of any successful team."
That's four sentences and zero information. It's timber with no brick — there's a frame, but nothing holding it up.
Strong answer: "To me, good communication means having a clear point and backing it up with something specific. When I briefed my director on a vendor issue last quarter, I didn't walk through the whole history — I said 'the vendor missed the SLA by two days, it affected one client, and here's the fix we're implementing.' She had what she needed in 20 seconds."
The second answer is the same length. It defines the concept, gives a specific scenario with a specific outcome, and demonstrates the skill rather than claiming it. A coach annotating this answer would point to three things: the definition is in plain English, the example is concrete enough to be challenged (which means it's credible), and the closing detail — "she had what she needed in 20 seconds" — shows the candidate understands the purpose of the communication, not just the format.
Don't Confuse This With STAR or Generic Interview Prep
STAR helps you tell a story, but it does not do the thinking for you
The interview answer framework most candidates know is STAR: Situation, Task, Action, Result. It's a useful structure, and it's worth knowing. But it's a container, not a filter. STAR tells you how to organize a story. It doesn't tell you which part of the story actually matters, or how much detail is enough, or when to stop.
The brick-and-timber idea operates at a different level. It's about whether you can identify the load-bearing point in your own message and make sure it's supported. STAR can help you do that — but it can also help you produce a very organized, very long answer that buries the useful sentence under three paragraphs of setup.
What this looks like in practice
Here's the same raw material handled two ways:
STAR answer that loses the thread: "The situation was that we had a client escalation in Q3. My task was to coordinate the response across three teams. I set up a daily standup, created a shared tracker, and drafted the client communication. The result was that the client was satisfied and we retained the account."
That's technically correct. It's also 50 words of setup for a one-sentence result, and the listener has no idea what made the resolution work.
Tighter answer using the same material: "We had a client escalation — they were ready to leave. I pulled three teams into one daily standup and we resolved the core issue in four days. The client stayed and we changed our escalation process because of it."
Same events. Half the words. The point lands because the structure serves the substance, not the other way around. A coach who has seen candidates hide behind STAR will recognize this pattern immediately: the framework becomes a way of filling time without making a judgment call about what actually matters. Brick and timber forces that judgment call.
Catch the Red Flags: Structure Without Substance, or Substance Without Structure
A clean answer can still be empty
The first failure mode is the polished-but-hollow answer. The communication structure is there — clear sentences, logical progression, confident delivery — but every claim is a generality. "I prioritize clarity." "I make sure the key points come first." "I tailor my message to the audience." These are not wrong. They are also not evidence of anything.
Interviewers who have been doing this for a while can spot this pattern quickly, and it tends to produce a specific reaction: the candidate seems capable but unverifiable. There's nothing to push back on, which means there's nothing to trust either.
What this looks like in practice
Structure without substance (polished but hollow): "I believe communication should be clear, concise, and audience-appropriate. I always think about what the listener needs to know and make sure I lead with the most important point."
Clean sentences. No information.
Substance without structure (dense but messy): "So there was this project last year where we had a lot of moving parts and the client kept changing the requirements and we were also dealing with a resourcing issue at the same time, and I ended up having to talk to like four different people to get everyone aligned, and eventually it worked out but it was really complicated."
Real experience. No usable point.
A useful hiring-manager rubric separates three signals: clarity (can I follow the logic?), evidence (is there a specific detail I could verify?), and judgment (did the candidate choose the right thing to emphasize?). According to the Bureau of Labor Statistics' Occupational Outlook Handbook, communication skills appear in the requirements for virtually every professional role — but the distinction between listing communication as a skill and demonstrating it is exactly the gap these red flags expose. The strong answer passes all three checks. The hollow answer passes only the first. The messy answer passes only the second.
How Verve AI Can Help You Prepare for Your Interview With Brick and Timber of Communication
The structural problem this article diagnosed — knowing the concept but blanking when someone asks you to explain it live — doesn't get solved by reading. It gets solved by saying the answer out loud, getting a response, and adjusting. That feedback loop is what's missing from most interview prep.
Verve AI Interview Copilot is built for exactly that loop. It listens in real-time to what you actually say — not a canned prompt you typed in — and responds to the specific answer you gave, including the parts you glossed over or the sentence that ran too long. When you're practicing a 30-second answer about communication structure, Verve AI Interview Copilot can catch whether you defined the concept, used a real example, and landed the point — or whether you gave the polished-but-hollow version that sounds fine until someone follows up. The desktop app stays invisible during screen-shared mock sessions, so you can practice in conditions that match the real thing. If you want to rehearse the brick-and-timber answer in a setting that responds to what you actually said rather than what you meant to say, Verve AI Interview Copilot is the right tool for that.
FAQ
Q: What does the phrase "brick and timber of communication" actually mean in plain English?
It means that clear communication requires two materials working together: structure (the timber — the logical frame that tells the listener where you're going) and substance (the brick — the specific detail or example that makes the message credible). Neither works without the other. A message with only structure is organized but empty; a message with only substance is dense but directionless.
Q: How would an interview candidate explain it without sounding generic or over-rehearsed?
Use a plain-English definition, then immediately give a specific example from your own work — a project update, a client conversation, a decision you had to explain. The example is what makes the answer sound real. If you memorize a definition and recite it, the interviewer will hear it. If you anchor the definition to something you've actually done, the answer sounds like yours.
Q: What is a strong example of using bricks and timber in a real interview answer?
"To me, it means having a clear point and backing it up with something specific. When I briefed my director on a vendor issue last quarter, I didn't walk through the whole history — I said 'the vendor missed the SLA by two days, it affected one client, and here's the fix.' She had what she needed in 20 seconds." That answer defines the concept, uses a real scenario with real detail, and shows the candidate understands the purpose of the communication.
Q: How can a career coach teach this concept as a repeatable framework?
Teach it as a two-question check candidates apply to every answer before they give it: "What is my point?" and "What specific detail proves it?" If they can answer both in one sentence each, the answer is ready. If they can answer only one, it needs work. The framework is most useful when candidates practice it on their own stories before the interview, not as a live editing tool under pressure.
Q: What should a hiring manager listen for when a candidate says they understand this idea?
Listen for whether the candidate can demonstrate it, not just describe it. The tell is specificity: does the candidate give a concrete example with a real detail — a number, a timeline, a named outcome — or do they explain the concept in general terms? A candidate who says "I make sure my communication is clear and structured" has described the idea. A candidate who says "I gave my manager a two-sentence update: the blocker, and the fix" has demonstrated it.
Q: How is this different from simply being prepared or using STAR?
Preparation is about having material ready. STAR is about organizing that material into a story. Brick and timber is about something more specific: whether you can identify the load-bearing point in your message and make sure it's supported by real evidence. You can be well-prepared and use STAR correctly and still give an answer that's organized but hollow. The brick-and-timber check is a filter on the quality of the content, not just the structure of the delivery.
Q: What are signs that someone has strong communication structure but weak substance, or vice versa?
Structure without substance looks like clean, confident sentences that contain no verifiable information — every claim is a generality, nothing could be followed up on. Substance without structure looks like a real story with real detail that never arrives at a point — the listener gets the facts but not the meaning. The strong answer passes three checks: the logic is followable (clarity), there's a specific detail present (evidence), and the candidate chose the right thing to emphasize (judgment).
Conclusion
That slightly stuck feeling — knowing the phrase matters, not quite knowing what to say — is exactly what this guide was designed to dissolve. You now have a plain-English definition of the brick and timber of communication that holds up under a follow-up question, a 20- to 30-second answer template you can actually say out loud, and a clear sense of what separates a strong answer from a polished-but-empty one.
The last step is the one most people skip: say the answer out loud before the interview. Not in your head, not typed into a notes app — out loud, to a friend, a mirror, or a mock interview tool. That's where you'll find out whether the example you chose sounds natural or borrowed, whether the definition lands or wanders, and whether you can actually hold the structure under mild pressure. The concept is simple. The practice is what makes it yours.
James Miller
Career Coach
