Platform Quality
Documentation
In-product help and public docs that match what actually ships, answers where you work, kept current with the platform.
Overview
Docs that lag the product are worse than no docs, they send people down dead ends. Thorbis is building in-product help and public documentation that stay in sync with what actually ships. You'll get answers right where you're working and reference material you can trust, so your team can self-serve instead of waiting on support for the basics.
What we're building
Docs that lag the product are worse than no docs, they send people down dead ends and erode trust in everything else you've written.
Thorbis is building in-product help and public documentation that stay in sync with what actually ships. You'll get answers right where you're working, plus reference material covering setup, workflows, and troubleshooting that you can rely on.
It's for teams that would rather self-serve than wait on support for the basics, current docs mean fewer tickets and faster onboarding.
What you'll be able to do
- Surface help in-product where you work
- Keep public docs matched to shipped features
- Let teams self-serve common questions
- Cover setup, workflows, and troubleshooting
- Reduce reliance on support for the basics
- Find answers without leaving the screen you're on
- Trust docs that stay in sync with what shipped
Rollout plan
- 01
In-product help
In progressSurface answers right where you're working.
- 02
Public reference docs
In progressPublish setup, workflow, and troubleshooting docs matched to shipped features.
- 03
Stay-in-sync upkeep
In progressKeep help and docs current as the platform changes.
Milestones
- Not started:
Doc coverage mapped
Identify the setup, workflow, and troubleshooting topics to cover.
- Not started:
In-product help surfaced
Put help where users work.
- Not started:
Public docs published
Ship reference docs matched to the product.
- Not started:
Sync process in place
Keep docs aligned with what ships.
More in Platform Quality
How to send useful feedback
Name the blocked role
Product feedback is more useful when it names the owner, dispatcher, technician, office user, or customer affected.
Explain the workaround
Describe what your team does today and where the process fails under real work.
Define success
Share what would change after launch: time saved, fewer manual steps, cleaner records, or better customer follow-up.