~/talk

Project Management for Engineers

slides:none on file

Practical framework for engineers who end up managing projects: adopt an Impact Effort Matrix, use a single shared Google Doc for planning, run a one quarter trial for any process change, and require a migration plan and SOP so improvements stick. Track outcomes with success statements (~100–200 chars) like “increased sales 15% via third‑party API,” “reduced storage costs $500/mo,” or “saved 60 minutes/week with automation.” Expect velocity gains if administrative glue work is assigned and limited.

AI-written summary · about

  1. 0:00Introduction
  2. 3:11Building team consensus
  3. 9:54Impact effort matrix
  4. 17:37Stakeholder prioritization
  5. 23:16Success statements
  6. 28:42Bragging to management
  7. 31:30Documenting processes
  8. 35:51Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.