Top CTO's Advice: The Real Reason You Are Not Growing | Sauvik Banerjjee | FO558 Raj Shamani
Executive Summary
Sauvik Banerjjee discusses execution, accountable teams, dated commitments, clear product notes and respectful disagreement with leaders. Selected workplace coverage; AI demo, later AI discussion and personal-loss passages omitted. Auto-captions have recognition errors and no speaker labels; attribution follows the question-and-answer context. Advice and company examples are his views, not universal rules or verified current policies. Untimed topics are not video chapters. Source: https://www.youtube.com/watch?v=XwawXRaNfzM
Key Takeaways
Show enough work to learn
Banerjjee contrasts lengthy conceptual work with a team member who assembled and demonstrated an imperfect product. He values learning while building rather than waiting for perfection. This does not remove the need for testing or care when money, customers or safety depend on the result.
Make responsibility visible
He describes a framework of responsible, accountable, consulted and informed roles. Captions misrecognize the acronym, but the roles are explicit. Naming who drives the work and who needs consultation can reduce uncertainty about handoffs without replacing agreement on the actual task.
Compare commitments with delivery
His say-do ratio compares what a team says it will deliver with what it does. He uses team examples to illustrate reliability rather than effort alone. Before measuring the ratio, make the commitment clear enough that everyone can tell whether it was met.
Include a date and time
He says reviews of commitments need a date and time, using Tuesday afternoon as an example. A task can sound agreed while its timing remains vague. Write the deadline with the expected result, then report progress against that promise rather than move the meaning after the fact.
Do not confuse effort with advancement
Asked whether the hardest worker usually rises, he says hard work needs intelligence too. His view is that effort alone is not a complete explanation of progress. This is workplace opinion, not a measured promotion rule or a judgment that people who struggle are not trying.
Describe the finished product in writing
He praises writing a product note as a press release so the end result is clear before building it. The proposed product can then be discussed in a shared document. His comments about memory and presentation formats are opinions; the practical step is to make the expected result concrete.
Disagree with respect and a specific view
He suggests a low, respectful voice and an opening that acknowledges the leader's view before asking for time to explain a different one. Tone can help the conversation without guaranteeing a receptive boss. Preserve the actual disagreement rather than soften it until the decision-maker cannot understand it.
The Conversation Breakdown
Show enough work to learn
⏱ Untimed topicBanerjjee contrasts lengthy conceptual work with a team member who assembled and demonstrated an imperfect product. He values learning while building rather than waiting for perfection. This does not remove the need for testing or care when money, customers or safety depend on the result.
Make responsibility visible
⏱ Untimed topicHe describes a framework of responsible, accountable, consulted and informed roles. Captions misrecognize the acronym, but the roles are explicit. Naming who drives the work and who needs consultation can reduce uncertainty about handoffs without replacing agreement on the actual task.
Compare commitments with delivery
⏱ Untimed topicHis say-do ratio compares what a team says it will deliver with what it does. He uses team examples to illustrate reliability rather than effort alone. Before measuring the ratio, make the commitment clear enough that everyone can tell whether it was met.
Include a date and time
⏱ Untimed topicHe says reviews of commitments need a date and time, using Tuesday afternoon as an example. A task can sound agreed while its timing remains vague. Write the deadline with the expected result, then report progress against that promise rather than move the meaning after the fact.
Do not confuse effort with advancement
⏱ Untimed topicAsked whether the hardest worker usually rises, he says hard work needs intelligence too. His view is that effort alone is not a complete explanation of progress. This is workplace opinion, not a measured promotion rule or a judgment that people who struggle are not trying.
Describe the finished product in writing
⏱ Untimed topicHe praises writing a product note as a press release so the end result is clear before building it. The proposed product can then be discussed in a shared document. His comments about memory and presentation formats are opinions; the practical step is to make the expected result concrete.
Disagree with respect and a specific view
⏱ Untimed topicHe suggests a low, respectful voice and an opening that acknowledges the leader's view before asking for time to explain a different one. Tone can help the conversation without guaranteeing a receptive boss. Preserve the actual disagreement rather than soften it until the decision-maker cannot understand it.
Core Frameworks & Ideas
Say-do ratio
Compare explicit commitments with what was delivered, tied to a date and time.
Responsible, accountable, consulted, informed
Name the roles around a project; the caption acronym is unreliable but the four roles are stated.
Product press release
Describe the intended product result in writing before the team builds it.
Actionable Next Steps
- ✓Write the expected result and deadline for one commitment.
- ✓Name who drives a project and who needs consultation.
- ✓Draft a plain-language description of a finished product.
- ✓Prepare a respectful opening and specific alternative before disagreeing.
Notable Quotes
“What you say and commit and what you do and deliver.”
“Tuesday afternoon means Tuesday afternoon.”
“Give the leader the respect”
The One Thing to Remember
Make a clear, dated commitment, deliver against it and explain disagreement without hiding it.