When the product plan changes

A product team changes its plan and dates and assignments also have to change in the rollout document other teams use. The document assistant Superhuman announced on November 19 can take on that second job. A trigger the team sets in advance can start the work even when the document is closed. In the company's example, an update to the product plan prompts the assistant to edit the rollout document that depends on it.[1]

Changing a date in the rollout document and deciding which team owns it are different jobs. One puts a decision already made into the document. The other changes somebody's workload. If the person assigning the assistant's work decides in advance which decisions it can copy directly into the document, it becomes clearer which changes still need a conversation between teams.[1]

Who gives permission, who reads the result

Superhuman says the version history shows what the assistant changed and who authorized the action. That can make the job easier for whoever reviews the edit later. The review still has to appear on somebody's task list. If the author of the plan grants broad permission to edit, for example, the team carrying out the plan may be left to spot each change in delivery dates.[1]

Superhuman has opened the Go development kit to outside developers. It says the document assistants are due in open beta for self-serve customers on December 1. The first time a team uses one might be a change in plan that gives everyone new work. On that day, who checks whose work has changed matters as much as who prepared the document.[1]