Coward

Podcast 2 — In conversation

Speaker A: He knew the project was going badly wrong but said nothing to the board. That kind of silence is cowardice — moral cowardice, specifically.

Speaker B: Moral cowardice as a professional failure — the silence when truth requires speech. It is arguably more damaging than physical cowardice in most organisational contexts, because it's precisely the moments when someone in a meeting knows something important and fails to say it that decisions go catastrophically wrong. Moral cowards abound in every organisation.

Speaker A: She called the decision a coward's choice — taking the safe option that avoided any risk rather than the bold one that might actually change things.

Speaker B: Coward as a moral evaluation of a decision rather than a person — the coward's choice is the one driven by fear of consequences rather than by what is right or effective. It is possible to make a cowardly choice without being a coward in general — one act of avoidance, one moment of choosing safety over courage.

Speaker A: Using anonymous feedback to complain about a colleague instead of raising it directly is the coward's approach. If you have a problem with someone, you tell them.

Speaker B: Coward as a critique of anonymity used as a shield — the feedback mechanism that allows criticism without accountability. There is legitimate use for anonymity in some contexts; but when it is used specifically to avoid the discomfort of direct conversation, it slides into cowardice. Courage in professional relationships often means saying to someone's face what you would rather say behind their back.

Speaker A: People sometimes confuse coward and cowardly.

Speaker B: Coward is the noun — a person. Cowardly is the adjective — describing an action or a quality. You call a person a coward; you describe their act as cowardly. A cowardly attack. A coward ran away. The distinction is grammatical: coward is what someone is; cowardly is how something is done.

Speaker A: And coward is different from timid. Timid means shy or nervous by temperament — it is a personality description without strong moral judgement. A timid person may avoid confrontation but not because they know they should face it and choose not to. Cowardice specifically implies that the person knows the right thing is to be brave and chooses fear instead. Timid is descriptive; coward is morally evaluative.

Podcast 3 — Prompt engineering

Speaker B: Scenario one — an error handling design prompt.

Review this API error handling code for coward patterns — places where the code silently swallows errors, returns empty results instead of meaningful error messages, catches exceptions without logging or rethrowing, or uses a catch-all fallback that hides the real failure. For each coward pattern found, explain why it is problematic and suggest the brave alternative: specific error types, meaningful error messages, proper logging, and failure modes that surface problems rather than hiding them behind silent fallbacks.

Speaker B: Coward pattern as a code review concept — errors that hide behind silent fallbacks rather than surfacing the real problem. A coward catch block that returns null instead of throwing is doing exactly what the etymology predicts: tucking its tail between its legs and hoping nobody notices.

Speaker A: The brave alternative — specific error types, meaningful messages, proper logging — is the code that faces the failure directly and tells you exactly what went wrong and where.

Speaker B: Next — a risk management prompt.

Design a risk decision tracking system for a product team that flags coward decisions — choices made to avoid risk rather than to maximise value. For each significant product decision, the system captures: the options considered, the option chosen, the reason for the choice, and whether the choice was risk-driven (avoiding a bad outcome) or value-driven (pursuing a good outcome). A weekly report shows the ratio of risk-avoiding to value-pursuing decisions, flags decisions identified as coward choices by the team retrospective, and tracks whether coward decisions subsequently proved justified or merely avoided necessary action.

Speaker A: Ratio of risk-avoiding to value-pursuing decisions over time is the product courage metric — a team making mostly risk-avoiding choices is probably not building the boldest, most differentiated product it could.

Speaker B: Right. Now an honest feedback system prompt.

Build a direct feedback system for a performance management platform that prevents coward feedback — vague, non-committal assessments that avoid saying anything substantive to avoid discomfort. The system: requires feedback givers to provide at least one specific example for every rating below satisfactory, flags feedback that uses only positive language regardless of the performance rating (detecting positive-only coward reviews), requires managers to confirm they have discussed the feedback directly with the employee before submitting, and shows the manager a direct conversation guide for delivering difficult feedback without retreating into coward generalities.

Speaker B: Detecting positive-only feedback regardless of rating is the coward review flag — a review that gives someone a poor rating but only uses positive or neutral language is the definition of moral cowardice in performance management.

Speaker B: Fourth — an architecture decision prompt.

Analyse this software architecture proposal for coward design patterns: technical debt deferred rather than addressed, known scaling bottlenecks left in place to avoid rework, overly conservative technology choices made to avoid learning rather than to serve the problem, and abstraction layers added to avoid dealing with a messy reality rather than to improve the design. For each coward pattern identified, explain the short-term cost avoided and the long-term cost deferred, and suggest what the brave architectural choice would look like.

Speaker A: Abstraction layers added to avoid dealing with messy reality rather than to improve design is the coward abstraction pattern — wrapping a bad database schema in an elaborate ORM layer instead of fixing the schema is the architectural equivalent of the tail between the legs.

Speaker B: Fifth — a moral courage training prompt.

Design a workplace moral courage training module for a leadership development platform. The module covers: the definition of moral cowardice in professional contexts (silence, deflection, euphemism, and anonymous complaint as alternatives to direct honest speech), five common scenarios where moral cowardice appears in organisations (the bad performance review, the unsafe practice ignored, the bad idea praised, the credit taken wrongly, the complaint made anonymously), the psychological mechanisms that make moral cowardice feel safer than courage, and a practice exercise where learners choose between the coward response and the courageous one in each scenario.

Speaker B: Psychological mechanisms making moral cowardice feel safer is the self-awareness teaching — understanding why we choose the coward path makes it easier to recognise and resist the choice.

Speaker B: Sixth — a full small app.

Build a single-page web app called Courage Log — a personal moral courage tracker. The user logs moments when they chose the brave action over the coward path: speaking truth when silence was easier, making a difficult phone call instead of sending a vague email, raising a concern in a meeting rather than grumbling privately. Each entry has a date, a description of the situation, what the coward choice would have been, and what they actually did. The app shows entries in chronological order as a courage journal and a monthly count of logged courageous actions. All data in localStorage.

Speaker A: Logging what the coward choice would have been alongside what they actually did makes the courage explicit — you can only appreciate the act of courage if you acknowledge the easier path not taken.

Speaker B: That's the lesson — a coward's tail is between their legs, and it has been since the Old French gave us the word. Moral cowardice is the failure to do or say what is right because doing so is uncomfortable. In code, in architecture, in feedback, and in leadership, the coward path is always available — the safe fallback, the vague word, the silent meeting. The brave choice is always harder and almost always better.

Speaker B: Prompt example: