There’s so many tools out there, but what are the best for managing development teams? Paul Schreiber, Developer at FiveThirtyEight, will walk through best practices and tools for workflow, automation and testing, along with good practices for managing development teams.
Central Line Insertion Care Team Checklist
Date____________________ Time____________________ Addressograph
TYPE OF LINE PLACED ______________________ REWIRE អ LOCATION OF LINE ____________________ # OF LUMENS ___________
Directions: The Assistant completes this checklist by indicating with a checkmark in the
appropriate column when the task is performed. If the task is not performed, a comment
must be added. The Supervisor may also function as the Assistant who completes this form.
Yes Yes with Reminder
(If No-add a
1. Perform a time out using the informed consent form.
2. Clean hands
3. Wear cap, mask, sterile gown/gloves, and eye protection if in
contact with or crossing the sterile ﬁeld *at any time during the
a. All others entering the room during the procedure must wear
cap and mask.
4. Prep site with chlorhexidine and let air dry. (*See instructions)
5. Drape patient from head to toe using sterile technique.
6. Prepare catheter by pre-ﬂushing and clamping all lumens not in
use during procedure.
7. Place patient in trendelenburg position unless contraindicated
(e.g., increased ICP) or if femoral/ PICC (place supine and ﬂat).
8. Maintain sterile ﬁeld.
9. Ensure grasp on guide wire is maintained throughout procedure
and removed post procedure.
អ Johns Hopkins Hospital
អ Johns Hopkins Bayview
អ Other: _______________________________
understand what people need
Early in the project, spend time with
current and prospective users of the
Use a range of qualitative and
quantitative research methods to
determine people’s goals, needs, and
understand what people need
Test prototypes of solutions with real
people, in the field if possible
Document the findings about user goals,
needs, behaviors, and preferences
Share findings with the team and agency
understand what people need
Create a prioritized list of tasks the user
is trying to accomplish, also known as
As the digital service is being built,
regularly test it with potential users to
ensure it meets people’s needs
AA CCHHEECCKKLLIISSTT FFOORR CCHHEECCKKLLIISSTTSS
Do you have clear, concise
objectives for your checklist?
Is each item:
A critical safety step and in great
danger of being missed?
Not adequately checked by other
Actionable, with a specific
response required for each item?
Designed to be read aloud as a
One that can be affected by the
use of a checklist?
Have you considered:
Adding items that will improve
communication among team
Involving all members of the team
in the checklist creation process?
Does the Checklist:
Utilize natural breaks in workflow
Use simple sentence structure and
Have a title that reflects its
Have a simple, uncluttered, and
Fit on one page?
Minimize the use of color?
Is the font:
Upper and lower case text?
Large enough to be read easily?
Dark on a light background?
Are there fewer than 10 items per
Is the date of creation (or revision)
Trialed the checklist with front line
users (either in a real or simulated
Modified the checklist in response
to repeated trials?
Does the checklist:
Fit the flow of work?
Detect errors at a time when they
can still be corrected?
Can the checklist be completed in
a reasonably brief period of time?
Have you made plans for future
review and revision of the
$ git bisect start
$ git bisect bad master
$ git bisect good 256d850
Bisecting: 29 revisions left to test
after this (roughly 5 steps)
02] FTC newsletter: make headline and
body text links black
Bisecting: 14 revisions left to test
after this (roughly 4 steps)
b0] Pass data-page-url through
matchProtocltoWindow to fix extraneous
$ git bisect good
Bisecting: 7 revisions left to test
after this (roughly 3 steps)
5a] The use of self:: outside of a
class context was causing fatal errors,
this fixes those errors for now
$ git bisect bad
Last year, I submitted a story to EWB’s Failure Report
on the failure of communication between parts of
EWB – the failure of a knowledge management sys-
tem. In brief: in December 2010, I had a meeting with
an Edmonton MP where I discovered that he already
had a relationship with EWB at the national level. So
much so, that he was attending EWB’s National Con-
ference in January prior to visiting Ghana with EWB.
In the time since this failure was published in the
Failure Report, what has changed? From my perspec-
tive – very little. There is some movement for an MP
relationship tracking tool, but there hasn’t (yet) been
broad support for it and there is still minimal sharing
between National Office and chapters in the realm of
MP knowledge and actions.
So why didn’t we learn from the Failure Report? Here’s
a look at the process of the Failure Report, from my
A person or a specific group experiences the failure
and the consequences of that failure. When submis-
sions to the Failure Report are advertised openly, they
may share it, and it eventually it ends up in the year’s
Report, distributed at National Conference in January
and occasionally referenced afterwards.
Within this process, I see three failures:
• The right people don’t necessarily learn from
the submitted failures. There is misalignment
between who experiences the consequences of a
failure, and who can solve for it at its root cause.
• The Failure Report emphasizes individual solu-
tions, and puts the onus on one person to learn
or “fix” the failure. This does not facilitate broad
learning from the mistake, and does not incite
institutional change to avoid the same failure.
• Very little follow-up occurs after the Failure Re-
port is distributed at National Conference, with
the exception of learning at an individual level.
Looking at the failure I submitted last year, it is the
quality of EWB’s advocacy work that suffers. In this,
Leadership & Organizational Change
Many graphics from The Noun Project
Hospital by Nimal Raj; Calendar by Laurent Canivet; Computer by Azis;
Phone by Fasobrun Jamil; Password by b farias; Checklist by David;
Script by Yuri Mazursky; Okay by Akhil Komath; insect by Hopkins;
Lock with keyhole by Brennan Novak; Package by Rockicon; Snail by
aLf; Robin by Xavier Gironès; Light by Numero Uno; Stick by Blaise
Sewell; Gears by Gregor Cresnar; Search by Aneeque Ahmed; Person
by asianson.design; Surfboard by Stanislav Levin.; cycle by lipi; Return
by Robert Bjurshagen; File by Creative Stall; Star by Thays Malcher;
Ghost by Rafael Garcia Motta; running by Abraham; clock by Gregor
Cresnar; Personal by Yaroslav Samoylov; mortar board by john melven;
Thought bubble by by b farias.