liveBook · Manning

Responsibility

A responsibility is a duty, capability, or area of accountability assigned to a person, role, class, object, or other entity.

How 2 Manning books explain it

Software Architecture Decision-Making

The explicit accountability for maintaining architectural coherence, revisiting assumptions, and protecting important system qualities over time.

How it is used
Frames ongoing accountability for architectural coherence through delivery, operations, feedback, and change.
How deep it goes
Explains responsibilities, organizational ownership models, feedback signals, and evolutionary trade-offs without prescribing implementation procedures.
Examples
Contrasts a solution architect with shared staff-engineer and team-lead ownership, and identifies incidents, audits, migrations, and cost reviews as signals.
What you can do after
Evaluate/understand whether ownership, decision memory, protected qualities, and feedback-driven adaptation are explicit.

Read how Software Architecture Decision-Making explains responsibility →

Lead Developer Career Guide

A task or duty for which a person in a role is accountable.

How it is used
Frames accountability as a foundation for lead-developer leadership, communication, delegation, and team support.
How deep it goes
Defines responsibility against expectations, then gives workplace duties, delegation guidance, feedback cautions, and client examples.
Examples
Uses lead-developer duties, client misunderstandings, contract disputes, delegation choices, and feedback conversations as examples.
What you can do after
Apply it by clarifying duties, communicating across roles, delegating work, giving feedback, and realigning disputed expectations.

Read how Lead Developer Career Guide explains responsibility →

Also covered in

What to know first

Related concepts

Questions about responsibility

What is responsibility?

A responsibility is a duty, capability, or area of accountability assigned to a person, role, class, object, or other entity.

Which Manning books explain responsibility?

Software Architecture Decision-Making and Lead Developer Career Guide.

What should I know before learning responsibility?

Manning books that teach responsibility usually introduce attribute, design pattern, implementation and object first.

What is the difference between responsibility and expectation?

A responsibility is a duty, capability, or area of accountability assigned to a person, role, class, object, or other entity. An expectation is an anticipated standard, condition, behavior, performance level, or outcome associated with a person, system, process, or interaction.

What kinds of responsibility are there?

Kinds of responsibility include fiduciary responsibility, corporate social responsibility and operational responsibility.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.