> - many meetings can be replaced by an update email

Highlights from the feed(s); GitLab has the better activity view IMHO but I haven't tried the new GitHub Issues beta yet.

3 questions from 5 minute Stand-Up Meetings (because everyone's actually standing there trying to leave) for Digital Stand Up Meetings: Since, Before, Obstacles:

  ## 2021-09-28
  ### @teammembername
  #### Since
  #### Before
  #### Obstacles

Since: What have you done since last reporting back? Before: What do you plan to do before our next meeting? Obstacles: What needs which other team resources in order to solve the obstacles?

You can do cool video backgrounds for any video conferencing app with pipewire.

You can ask team members to prep a .txt with their 3 questions and drop it in the chat such that the team can reply to individual #fragments of your brief status report / continued employment justification argument

> - decisions often work better through docs + feedback than big meetings

SO, ah, asynchronous communication doesn't require transcripting for the "Leader Assistant" that does the Mando quarterly minutes from the team chat logs, at least

6 Patterns of Collaboration: GRCOEB: Generate, Reduce, Clarify, Organize, Evaluate, Build Consensus [Six Patterns]; voting on specific Issues, and ideally Chat - [x] lineitems, and https://schema.org/SocialMediaPosting with emoji reactions

[Six Patterns]: http://wrdrd.github.io/docs/consulting/team-building#six-pat... , Text Templates, Collaboration Checklist: Weighted Criteria, Ranked-choice Voting.

Docs and posts with URLs and in-text pull-quotes do better than another list of citations at the end.

> - you don't need frequent contact with the team if the goals and constraints are communicated very clearly

Metrics: OKRs, KPIs, #GlobalGoals Goals Targets and Indicators

Tools / Methods; Data / Information / Knowledge / Experience / Wisdom:

- Issues: Title, - [ ] Description, Labels, Assignee, - [ ] Comments, Emoji Reactions;

- Pull Requests, - [ ] [Optional] [Formal] Reviews, Labels & "Codelabels", label:SkipPreflight, CI Build Logs, and Signed Deployed Documented Applications; code talks, the tests win again, docs sell

- Find and Choose - with Consensus - a sufficiently mature Component that already testably does: unified Email notifications (with inbound replies,) and notifications on each and every Chat API and the web standard thing finally, thanks: W3C Web Notifications.

- Contribute Tests for [open source] Components.

- [ ] Create a workflow document with URLs and Text Templates

- [ ] Create a daily running document with my 3 questions and headings and indented markdown checkbox lists; possibly also with todotxt/todo.txt / TaskWarrior & BugWarrior -style lineitem markup.

What does an engineering manager do all day?

A polite answer would be, continuously reevaluate the tests of the product and probably also the business model if anyone knew what they were up to in there