◇ Could this help me?
Yes for the assembly pattern, with a firm limit on what the output should be used for. Pointing an assistant at the places work already happens, rather than asking people to maintain a second board that nobody updates, is a real insight, and a scheduled briefing that surfaces waiting approvals and stalled items is a legitimate use of connectors plus scheduled tasks. Two things need to be handled differently than the video suggests: connecting a workspace Slack and a shared Drive is a significant access decision that belongs to whoever owns that data rather than to whoever builds the dashboard, and a summary inferred from unstructured files is a prompt for a conversation, not evidence about a person's or a team's performance, so it should never be the basis of a judgment made without asking them. General practice.
I want a single view of what is in flight across several workstreams, built from the places work already happens rather than a separate tracker. Before connecting anything, tell me exactly what a Slack connector and a shared drive connector would be able to read, what stays out of reach, and what I should confirm with the people whose material would be included. Once I approve, generate a status view showing each workstream side by side: what was committed, what has not landed, what is behind schedule, and what is waiting on my approval. Mark every item with how you inferred it and how confident you are, and list separately the conclusions that need confirming with a person before I act on them. Then set up a scheduled morning briefing built from the same view.