-
Notifications
You must be signed in to change notification settings - Fork 180
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
M ◾ Updated "pencil in" rule (#9816)
* Updated "pencil in" rule * Auto-fix Markdown files * Update rules-to-better-software-consultants-dealing-with-clients.md * Update rule.md * Update rule.md --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
- Loading branch information
1 parent
3949380
commit 30a5019
Showing
4 changed files
with
62 additions
and
38 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
35 changes: 0 additions & 35 deletions
35
rules/do-you-always-pencil-in-the-next-date-on-your-last-day-at-the-client/rule.md
This file was deleted.
Oops, something went wrong.
2 changes: 1 addition & 1 deletion
2
...ake-sure-that-you-book-the-next-appointment-before-you-leave-the-client/rule.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,59 @@ | ||
--- | ||
seoDescription: Consulting clients with a clear plan for next steps ensures seamless project completion and reduces uncertainty. Book next appointments to avoid miscommunication and ensure a smooth workflow. | ||
type: rule | ||
title: Do you pencil in the next date before finishing a project? | ||
uri: pencil-in-the-next-booking | ||
authors: | ||
- title: Adam Cogan | ||
url: https://ssw.com.au/people/adam-cogan | ||
related: | ||
- being-a-good-consultant | ||
- book-developers-for-a-project | ||
redirects: | ||
- do-you-always-pencil-in-the-next-date-on-your-last-day-at-the-client | ||
created: 2010-07-16T06:38:09.000Z | ||
archivedreason: null | ||
guid: 6c65eb49-e31d-465d-9652-226b15e5d426 | ||
--- | ||
|
||
A common mistake for developers is to say _"See you later, call me sometime next month."_ | ||
|
||
If you don't create another appointment straight away, you and the client may forget. On your last day of consulting with a client, you should **always book in the next date**. | ||
|
||
<!--endintro--> | ||
|
||
::: info | ||
Be aware of the common blockage people get, which the client is saying _"How about I check my calendar and get back to you?"_ | ||
|
||
Often this never happens. | ||
::: | ||
|
||
A better approach is to minimize risk by saying **you’re penciling it in**, with the option to cancel or reschedule if needed. It is also a good idea to add urgency by mentioning that your calendar fills up quickly. | ||
|
||
::: greybox | ||
_"OK let catch up in say a month"_ | ||
::: | ||
::: bad | ||
Figure: Bad example - No appointment sent | ||
::: | ||
|
||
::: greybox | ||
_"My calendar fills up really quick, how about I pencil you in... say in 2 weeks' time?"_ | ||
|
||
Then create the appointment rather than remembering it later. | ||
|
||
_"Don't forget you can cancel or reschedule it anytime."_ | ||
::: | ||
::: good | ||
Figure: Good example - Proactively sending an appointment, bringing up urgency and options | ||
::: | ||
|
||
::: good img-medium | ||
 | ||
::: | ||
|
||
## What if it is your last day at the client, and you are not finished? | ||
|
||
If, at the end of the day, work hasn't been fully tested or is incomplete and you haven't been booked in for the next day, tell the Product Owner (PO) that issues may arise and further work is likely to be required. After the conversation, email the PO and Cc your manager to confirm that further work is required. | ||
|
||
E.g. _"As per our conversation, this work has not yet been tested and may still include bugs. At this stage, you would prefer if we did not continue to work tomorrow, but I do recommend that we come in and finish soon."_ |