Introduce a tool to your team
Start with a task people already want to improve: requests spread across email, approvals that need repeated follow-ups, or a tracker nobody keeps current. Agree what would make that task easier before asking someone to build.
Choose the first task
Section titled “Choose the first task”Ask the people doing the work where they get stuck. Pick one task with a clear owner and an existing data source, such as a shared Sheet.
Write down what success looks like in practical terms: people can find the status of a request without asking, or a manager can see which approvals need attention.
Try it with a few colleagues
Section titled “Try it with a few colleagues”Ask someone who knows the task to build a first version. Test it with the people who will use it. The builder’s sample-data preview is a starting point; check the deployed tool and data access with real work accounts before publishing widely.
For a form that saves records, agree how you will identify and remove test entries.
Agree who looks after it
Section titled “Agree who looks after it”Name someone for questions and updates, and an editor who can help when they are away. IT manages company access and can arrange a handover if the owner leaves.
People who only use the app are free. Anyone who builds or edits it needs an Applane seat. Your company also pays Google for Cloud usage. Pricing.
Share the link and the task
Section titled “Share the link and the task”Tell colleagues what the tool is for, when to use it and who to contact. Send the published link with the short guide to using it.
After people have used it, ask whether it reduced the follow-ups or confusion you started with. Use that feedback to choose the next change before extending the tool to more teams.
For AI agents: llms.txt, llms-full.txt, or any page with a .md suffix.