From c98d0b3a461583de62839094d2b20453acf89bdd Mon Sep 17 00:00:00 2001 From: Mike McNeil Date: Mon, 6 Sep 2021 19:08:49 -0500 Subject: [PATCH] Kick off the customer success handbook section (#1896) * Kick off the customer success handbook section * say it in fewer words --- handbook/README.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/handbook/README.md b/handbook/README.md index 199d9c03ef..3ea51a385e 100644 --- a/handbook/README.md +++ b/handbook/README.md @@ -151,6 +151,20 @@ or > Osquery and Fleet provide structured, convenient access to information about your devices. +### Customer succcess + +#### Next steps after a customer conversation +After a customer conversation, it can sometimes feel like there are 1001 things to do, but it can be hard to know where to start. Here are some tips: + +##### For customer requests +- Locate the appropriate issue, or create it if it doesn't already exist. (To avoid duplication, be creative when searching GitHub for issues- it can often take a couple of tries with different keywords to find an existing issue.) +- Is the issue clear and easy to understand, with appropriate context? (Default to public: declassify into public issues in fleetdm/fleet whenever possible) +- Is there a key date or timeframe that the customer is hoping to meet, please note that in the the issue. +- Make sure the issue has a "customer request" label. +- Post in #g-product with a link to the issue to draw extra attention to the customer request so it is visible ASAP for Fleet's product team. +- Have we provided a link to that issue for the customer to remind everyone of the plan, and for the sake of visibility, so other folks who weren't directly involved are up to speed? (e.g. "Hi everyone, here's a link to the issue we discussed on today's call: […link…](https://omfgdogs.com)") + + ### About the handbook #### Why bother? The Fleet handbook is inspired by (and heavily influenced by) the [GitLab team handbook](https://about.gitlab.com/handbook/about/). It shares the same [advantages](https://about.gitlab.com/handbook/about/#advantages) and will probably undergo a similar [evolution](https://about.gitlab.com/handbook/ceo/#evolution-of-the-handbook).