Communication Analysis: Max Votek

Across 3 meetings: Apr 21, Apr 28, Apr 30 — Persuasiveness, Clarity, Actionability, English
← Back to Tracker
7.0
Persuasiveness
6 → 8 → 7
7.0
Clarity
6 → 7 → 8
6.3
Actionability
5 → 7 → 7
7.0
English
7 → 7 → n/a
Scores by Meeting
Persuasiveness
Clarity
Actionability
English
Apr 21
6
6
5
7
Apr 28
8
7
7
7
Apr 30
7
8
7
Russian
Trend Visualization
Apr 21
6.0
Apr 28
7.3
Apr 30
7.3
Average across all metrics per meeting (English excluded for Apr 30)
Metric 1
7.0 Persuasiveness

How effectively you move people toward your position. Do they buy in? Do they act?

Apr 21 — Score: 6/10
"We don't need the traditional heads like PM, solution lead, functional consultant. So they're all being compressed. So, you can do like with Claude, you can do a lot of things on your own, right?" TELLING, NOT SELLING 7-minute monologue. Strong vision but no audience engagement. Nobody was asked for input or buy-in during the block.
What worked
Clear "scissors effect" concept. Strong conceptual framing. Genuine passion is felt.
What didn't
Monologue format — 7 min uninterrupted. You told the team the conclusion instead of walking them to it. No check-ins like "does this resonate?" or "what do you think?"
Apr 28 — Score: 8/10
"But guys, so like looking at this, I see that there is a communication gap. Right? So like in ideal world, Valeria should be able to access the same Claude session and be able to ask herself." PROBLEM → SOLUTION Named the gap, proposed the fix, got immediate buy-in from Mohammad ("I 100% agree").
"Yeah, maybe Mohamed. So I can take it like thirty forty minutes to help... with the basics of the operating system, how to use Playwright for testing, how to execute commands via CLI..." VOLUNTEERED Offered personal time + specific curriculum. More persuasive than asking someone else to do it.
What worked
Identified the problem first (communication gap), then proposed concrete solutions. Volunteered yourself. Interactive — got responses and agreement.
What didn't
The video generation pitch (avatars, Maksim Shcherbak) was a bit tangential — audience didn't respond to it. Felt like a feature demo rather than solving someone's problem.
Apr 30 — Score: 7/10 (in Russian)
"Not once, during the entire time we've been doing this project, has any consultant said 'let me show you how I configure this.'" SHARP OBSERVATION Crystallized months of frustration into one clear, undeniable sentence.
"We basically wasted 3 months. If this had been there from the start..." HONEST BUT BLUNT True and needed, but retrospective blame can make people defensive. Better: "Here's what we now know — and how we prevent this going forward."
What worked
Very direct. The "not once" observation is a powerful rhetorical device — undeniable and memorable. Jaspal suggestion was concrete.
What didn't
"3 months wasted" is backward-looking. More persuasive framing: "We've learned something that will save us 3 months on every future project."
Metric 2
7.0 Clarity

How easy it is to follow your point. Can the listener replay your message in their head?

Apr 21 — Score: 6/10
"So like the overall the team is like in a learning by doing phase right now, right? So and the main priorities also not just to make to productize the knowledge, but also uh the adoption of the entire team. So every single person on this project should be able to perform it. And wear multiple hats and perform it on their own." DENSE 3 ideas in one breath: learning by doing, productization, team adoption. The listener has to unpack.
Pattern
You stack 4-5 ideas before the listener can absorb the first one. The 7-minute block had ~12 distinct concepts. Strong individually, overwhelming together.
Fix
One idea per breath. State it. Pause. Let it land. Then move to the next. Your ideas are good — they just collide in delivery.
Apr 28 — Score: 7/10
"I see that there is a communication gap. Right? In ideal world, they should come together, resolve this, recorded in GitHub. Max shared a pretty good result with the summary of learnings — several approaches which can be reused for the next customizing sessions." STRUCTURED Problem → ideal state → evidence. Three beats, easy to follow.
Improvement over Apr 21
Shorter blocks. You diagnosed a problem (gap), described an ideal (shared session), and cited evidence (Max's GitHub learnings). This is a repeatable structure.
Still present
Filler chains: "So like... right? So like..." appear 4x in one paragraph. They slow your rhythm and dilute authority.
Apr 30 — Score: 8/10 (in Russian)
"You need a subject matter expert you can sit with, and he says 'click here, don't click there.' When I know an application well, I automatically avoid things a newbie would do." VIVID AND SIMPLE Concrete image. Everyone immediately understands the gap.
Why highest clarity
In Russian you naturally use shorter sentences, concrete analogies, and direct phrasing. Less filler. The "click here, don't click there" image communicates the problem better than any abstract description.
Takeaway
Your Russian communication style is more direct. Try carrying that directness into English — fewer qualifiers, more vivid examples.
Metric 3
6.3 Actionability

Do your contributions produce concrete next steps with owners and deadlines? Or do they stay as ideas?

Apr 21 — Score: 5/10
"Taras for you. Like to see the priorities, to select less methods and to track this. So like let's start tracking our progress. Like how many MD files did we contribute? How many learnings?" DIRECTION WITHOUT DEADLINE "Let's start tracking" — but when? How? What's the first step? Taras got a vague assignment with no deliverable or date.
Pattern
You paint the destination beautifully but skip the first step. The team leaves thinking "that sounds right" but not "I know what I'm doing Monday morning."
Fix
End every vision block with: WHO does WHAT by WHEN. Even rough: "Taras, can you draft a progress template by Thursday?"
Apr 28 — Score: 7/10
"Yeah, let's do me and Max here because Max has more hands-on experience right now, and I can share my experience on how to use Claude. And no problem — we have access to Claude Code certification program." OWNER + SCOPE + RESOURCE Named himself as owner, defined the scope (CLI, Playwright, schemas), pointed to the resource (certification program).
Improvement
Volunteered, named co-lead (Max Shevchenko), defined topics, linked to certification resource. Much more actionable than Apr 21.
Still missing
No date. "Let's do this" but no "let's do this Wednesday." The training session still hasn't happened as of Apr 30.
Apr 30 — Score: 7/10
"Maybe bring Jaspal in to conduct some sessions, and let him just talk through it — a text transcript. He'll talk through the sequence: what, why." SPECIFIC SOLUTION Named the person (Jaspal), the format (text transcript), the content (configuration sequence). Very actionable.
"Let me write to him in the chat so he sets up this session to go through the gaps with Valeria and you." IMMEDIATE ACTION Committed to doing something right now. Best actionability moment across all 3 meetings.
English Language Analysis
7.0 English Usage

Grammar, vocabulary, fluency, filler words. Apr 30 was in Russian — used for contrast.

Grammar
Vocabulary
Fluency
Fillers
Overall
Apr 21
7
8
7
5
7
Apr 28
7
8
7
6
7
Apr 30
Russian — see contrast notes below
n/a
Recurring Filler Patterns
"So like... right? So like..." — appears 15+ times across Apr 21 and Apr 28 combined. This is your #1 verbal tic. Suggestion: replace with a pause. Silence is more authoritative than "so like."
"Right?" at end of sentences — used as a confirmation-seeking tag. 20+ occurrences. In moderation it invites agreement; overused it signals uncertainty. Try: Use "right?" only when you genuinely want feedback. Otherwise, end with a period.
Grammar Notes
"select less methods" → "select fewer metrics" LESS vs FEWERApr 21 — "less" is for uncountable nouns, "fewer" for countable.
"help the guard with the basics" → unclear referent UNCLEARApr 28 — "the guard" likely meant Valeria or the team. Proper nouns are clearer.
"how to use computer use" → "how to use Computer Use" REDUNDANCYApr 28 — "use" repeated. Say "how to use the Computer Use feature" or just "Computer Use."
Russian vs English: What Changes
Stronger in Russian
Shorter sentences. More direct phrasing. Fewer qualifiers. Concrete analogies ("click here, don't click there"). You get to the point faster and with more authority. Almost zero filler words.
Stronger in English
Better conceptual vocabulary (scissors effect, communication gap, role compression). More polished framing for strategic ideas. English forces you to structure more explicitly, which helps for external audiences.
Recommendations
1. End every strategic block with WHO-WHAT-WHEN. Your vision is strong — it's the landing that needs tightening. After painting the picture, say: "So concretely — [name], can you [specific task] by [date]?" This one change would move Actionability from 6 to 8.
2. Replace "so like... right?" with silence. A 1-second pause is more powerful than any filler. Try recording yourself in a low-stakes call and counting the "so like" chains. Awareness alone cuts them by 50%.
3. One idea per breath in English. In Russian you naturally do this. In English, you stack 3-4 concepts into one long sentence. Finish the thought. Stop. Let it land. Then move to the next.
4. Frame backward lessons as forward opportunities. Instead of "we wasted 3 months," try "we now have a playbook that saves 3 months on every future project." Same truth, more persuasive — especially with clients and leadership.
5. Check in during long blocks. After 60-90 seconds, pause and ask "does this track?" or "any reactions?" This converts monologue into dialogue and dramatically increases persuasion.
Overall Trajectory
3-Meeting Communication Trend
6.0 → 7.3 → 7.3
Clear upward trajectory from Apr 21 to Apr 28 (+1.3). Maintained in Apr 30. Biggest gains in persuasiveness (interactive style) and actionability (naming owners and solutions). The ceiling-breaker will be adding deadlines and replacing fillers with pauses.
Communication analysis generated from meeting transcripts — SPIFF/SPM AI Configuration Project