I'm experienced with Scrum but just learning about Kanban. There is
one aspect of Scrum which I am trying to compare against Kanban, that
is the pressure to produce as experienced by members of the team.

In Scrum development the team makes a commitment (to the product
owners and themselves) to finish a set of stories during each
iteration. Then each day in the daily standup, team members again
make commitments to their peers about which task(s) they plan to
finish that day.

These regular commitments in Scrum result in a perceived pressure for
individual team members to produce. This can result from peer
pressure, integrity (keeping one's word), increased ownership (having
made the commitments themselves, as opposed to having them dictated by
management), or simply fear (of appearing not to be pulling one's
weight relative to the rest of the team). These are all aspects of
the maxim "deadlines get things done".

This sense of pressure is not necessarily positive. While it can
result in increased output by each team member, it can also backfire
and cause some people to cut corners in the short term (declaring
tasks as "done" with poor quality or net positive technical debt), and
to cause others to experience burn-out in the long run.

How is this reflected in Kanban? I know that some units of work
(tasks/stories/CRs/whatever) can have individual deadlines. How does
the lack of other artificial deadlines (created and imposed by other
processes such as Scrum) help or hinder in Kanban?

Thanks,
-- Tim Uttormark