Google Docs auto-generated document summaries powered by a Pegasus-based ML model
Document readers struggle to keep up with the volume of incoming documents daily, while writers find composing summaries cognitively challenging and time-consuming.
Early fine-tuning corpora had inconsistencies and high variation across document and summary types, causing the model to be easily confused and unable to learn document-summary relationships.
Google deployed a distilled Pegasus-based summarization model in Google Docs for Workspace business customers, generating 1-2 sentence summary suggestions with significant improvements in serving latency and memory footprint.
Frequently asked questions
What did this team achieve with this AI workflow?
Google deployed a distilled Pegasus-based summarization model in Google Docs for Workspace business customers, generating 1-2 sentence summary suggestions with significant improvements in serving latency and memory fo…
What tools did this team use?
Google Docs, Pegasus, Transformer, BERT, GPT, T5, TPUs, NLU, NLG.
What results were reported?
Serving latency and memory footprint: significant improvements in latency and memory footprint; Model quality after distillation: quality was still on par with the original model; fine-tuning examples needed (Pegasus vs Transformer baseline): as few as 1,000 (source-reported, not independently verified).
What failed first in this deployment?
Early fine-tuning corpora had inconsistencies and high variation across document and summary types, causing the model to be easily confused and unable to learn document-summary relationships.
How is this back office ops AI workflow structured?
Document opened in Docs → ML model comprehends and generates → Writer reviews suggestion → Summary aids document navigation.