Compare commits

...

2 Commits

1 changed files with 2 additions and 2 deletions

View File

@ -15,7 +15,7 @@ and leadership positions, I have noticed a number of successful patterns, and
unsuccessful patterns. In this post I want to focus on one of the more
successful patterns: good information management.
Engineering managers are expected to have loads of information ready in their
Engineering managers are expected to have loads of information ready
at all times. The architecture of the systems their team is responsible for,
current project priorities, cross-team points of dependence or collaboration,
and a myriad of other snippets of information. It's a _lot_, but I don't think
@ -70,7 +70,7 @@ critical information about the projects that are being worked.
Some managers I know use running Google Docs or Spreadsheets to manage their
workload, which may work for personal task tracking, but I typically discourage
their use. They're not linkable and discoverable enough!c Many spreadsheets are
their use. They're not linkable and discoverable enough! Many spreadsheets are
write-once and read-once. By building and collaborating with a shared
information management scheme, the team and the managers can benefit from the
on-going "gardening" of information.