Aligning Customer Expectations. In the Complex World of Magento

Transcription

1 Aligning Customer Expectations In the Complex World of Magento

2 Brent Peterson Magento Evangelist Agency Coach Selfie Extraordinaire Wagento Commerce

3 Magento s flexibility comes from its broad codebase and deep configuration scheme.

4 So how do we best educate the client?

5 The Challenge To educate the client upfront what a successful project looks like.

6 The Solution : Client Education Two things to Focus on: Learn what the client has done in the past Create a clear statement of work

7 The Solution : Client Education Learn what the client has done in the past Creating a clear statement of work Adding work to a project will add time to the project.

8 The Solution : Client Education Learn what the client has done in the past Creating a clear statement of work Adding work to a project will add time to the project. A project can t be done as soon as the designs are complete.

9 The Solution : Client Education Learn what the client has done in the past Creating a clear statement of work Adding work to a project will add time to the project. A project can t be done as soon as the designs are complete. Even when discovery is done surprises may occur.

10 How is education realized? Performing discovery on both the client and the project.

11 How is education realized? Managing the assumptions that are inherent in a Magento project. Performing discovery on both the project and the client.

12 How is education realized? Communicating to the client how modules, products, servers and traffic will impact the performance. Managing the assumptions that are inherent in a Magento project. Performing discovery on both the project and the client.

13 How is education realized? Setting clear billing expectations. Communicating to the client how modules, products, servers and traffic will impact the performance. Managing the assumptions that are inherent in a Magento project. Performing discovery on both the project and the client.

14 How is education realized? Clear billing expectations. Communicating to the client how modules, products, servers and traffic will impact the performance. Managing the assumptions that are inherent in a Magento project. Discovery on both the project and the client.

15 Having a Trusting Relationship is Key The Most Valuable Business Commodity: Trust David K. William Forbes.com

16 The Basic Contract

17 What a basic SLA looks like Client asks for work. Agency does work. Client approves work. Client pays for work. - REPEAT. Start the conversation about expectations early on. Make it simple enough for everyone to understand. Reassure the client that we will fix bugs and errors.

18 The Good

19 The Good Expectations The good is going to be realized by how each party member manages the expectations of the project.

20 The Good Expectations The agency s ultimate responsibility is to manage the expectations. The good is going to be realized by how each party member manages the expectations of the project.

21 The Good Expectations The client fully participates in the project The agency s ultimate responsibility is to manage the expectations. The good is going to be realized by how each party member manages the expectations of the project.

22 The Good Constant Consistent Communication is Key The single biggest problem in communication is the illusion that it has taken place. George Bernard Shaw

23 Put it in writing! The Good

24 The Good Communicate Timelines Carefully explain the project process Communicate timelines upfront Explain why a delay is happening

25 The Good Communication Quality Low quality communication may result in lost trust of the client Always value ethical actions over expedient ones. - Jean-Luc Picard

26 The Good Communication Quality Balancing the Information Too much information may result in confusion.

27 The Good Calls and face to face meetings As often as needed during discovery Once a week with client during production Scheduled and impromptu after launch

28 The Good s Client would expect to see these frequently After launch a scheduled check in should be maintained

29 The Good Reporting Weekly timeline during production Daily status updates on tickets if needed Schedule delays Anything else the client needs to know!

30 The Good Changes During production changes need to be introduced immediately Add or remove items that will impact the timeline Discuss budget Post launch versus pre-launch

31 The Good Tools Good Project Management tools will help move the project along for both the client and the agency. It is important to educate the client and engage them to use and learn the tools. As every client is different and every project is different each interaction will be different.

32 The Good Respect Time Time is valuable Respect the time of others Ensure it is time well spent Deliver valuable content

33 The Bad

34 The Bad Sales and Accounting Giving quotes without proper discovery Poorly communicated time spent on issues Declaring Yes we can do that! (without discovery)

35 The Bad Development and Technical Why something is a great idea but bad in practice. (200 store views)

36 The Bad Development and Technical Decision makers without the technical knowledge to make technical decisions and not asking questions. Why something is a great idea but bad in practice. (200 store views)

37 The Bad Development and Technical Magento projects taken by developers who know nothing about Magento Decision makers without the technical knowledge to make technical decisions and not asking questions. Why something is a great idea but bad in practice. (200 store views)

38 The Bad Development and Technical Let the developer be the only one to communicate with the client! Magento projects taken by developers who know nothing about Magento Decision makers without the technical knowledge to make technical decisions and not asking questions. Why something is a great idea but bad in practice. (200 store views)

39 The Bad Project Management Poorly communicated requirements

40 The Bad Project Management Letting the customer tell you when the project will be done. Poorly communicated requirements

41 The Bad Project Management Waiting until the end of a project to communicate changes Letting the customer tell you when the project will be done. Poorly communicated requirements

42 The Bad Project Management Project managers with too many projects Waiting until the end of a project to communicate changes Letting the customer tell you when the project will be done. Poorly communicated requirements

43 The Bad Project Management Creating poor common practices: allowing phone calls to dictate the new work and not following up in writing Project managers with too many projects Waiting until the end of a project to communicate changes Letting the customer tell you when the project will be done. Poorly communicated requirements

44 The Bad Project Management Getting emotionally involved in a project Creating poor common practices: allowing phone calls to dictate the new work and not following up in writing Project managers with too many projects Waiting until the end of a project to communicate changes Letting the customer tell you when the project will be done. Poorly communicated requirements

45 The Ugly

46 The Ugly At some point the client becomes frustrated because what they are expecting is different than what the Agency can or will deliver.

47 Client comes to a Magento Partner with performance issues after going through a non-magento Agency. Problem: 200 store views 9000 categories slow website. Someone without Magento experience may not know that loading up Magento with so many store views and categories will slow things down. Possible Solution: Reduce the amount of store views and categories as well as heavily caching the website.

48 Client in a rush has a questionable timeline. The client tells the agency it has to be done and agency agrees to do it without thinking. Problem: Let the client dictate the entire project: Time line, delivery. Etc Possible Solution: Say no. Full stop. Give the client a reasonable timeline

49 Customer comes to agency after dealing with another Magento developer or agency. New agency needs to both launch the project as well as fix and/or learn everything that has already been done. Problem: Recover a failed implementation: How do you deal with a project as the next developer or the sixth developer? Possible Solution: Be honest with the client and agree that you are not going to be able to know everything about the project. Let the client know that problems will come up and the agency will be there to help.

50 What did we learn? Communication is King Understanding what everyone wants and not assuming. Get it in writing Tell the client when something changes Be honest with the client Having awkward conversations up-front.

51 Thank You