30 lines
2.4 KiB
Plaintext
30 lines
2.4 KiB
Plaintext
Team, I've had the opportunity to chat with many of you individually to discuss the action item list for Pipedrive. As a
|
|
reminder of the topics discussed on Monday, [here is the
|
|
recording](https://northpass.zoom.us/rec/share/jg6aA71ibeYtyj8lJh8hqehp29nxZWugSnSdyLlamrbyJx5kF_j2psQYXzNs02zF.H1nLH-8UyUnLDBGD).
|
|
The passcode is `8@^z6zJG`.
|
|
|
|
I can't impress enough upon everyone how time sensitive these items are. Kat and I are chatting with Pipedrive at 9:30am
|
|
EST on Tuesday to get a better understanding of the client's needs. With Gainsight's Recharge day on Monday and Poland being off on Tuesday, I'm a bit afraid we've lost some precious time here.
|
|
|
|
There are two tracks that we've committed to as a team for saving Pipedrive. They are the following:
|
|
|
|
1. Bartosz, Adam, and the engineering team will investigate all the items on [the spreadsheet](https://docs.google.com/spreadsheets/d/1CfiXSZankDRsBSYzVIMdW-M-7_oU0seqYozADoKLN1Y/edit#gid=937292276) that SE cannot solve for and report back to Joris and Allyson with an estimated time frame and resource spend needed to bring those features to light and parity for Pipedrive's needs. Joris and Allyson will then decide the best direction regarding engineering's findings and the planned roadmap.
|
|
|
|
2. Charlie and the SE team will clean up the code in Pipedrive's templates to improve efficiency. This will be done in
|
|
sandbox first and then moved to production if need be so that engineering can reproduce the delay behavior and investigate causes and areas of improvement.
|
|
|
|
Regarding one - have any findings been reported to Allyson/Joris yet? Joris is on PTO as of tomorrow, so please let
|
|
Allyson know what you find ASAP. In the meantime, Adam/Bartosz, do you have any information that Kat and I should know about that will help inform our discussion with Pipedrive on Tuesday?
|
|
|
|
Regarding two - today's discussion made clear that the delay behavior is not acting as expected in the sandbox. As
|
|
engineering needs to mimic this behavior as closely as possible, we will reinstate the templates and language picker in
|
|
production as early as possible tomorrow morning. Charlie, can you please make sure an SE in Poland makes these changes
|
|
to Pipedrive's Production academy as early as possible tomorrow so the engineering team can investigate?
|
|
|
|
I will inform Pipedrive this evening of this temporary change.
|
|
|
|
Big day tomorrow, and I hope we'll be able to uncover key information for Pipedrive. Please let me know if you have any
|
|
questions or concerns.
|
|
|
|
|