When people hear “technical ecommerce discovery,” they imagine architects drawing diagrams on the whiteboard. They also picture a group of developers discussing connecting all the systems.
I took part in many technical ecommerce discovery sessions during the last decade. Some of them were successful. Some were not.
Sessions oriented primarily on technical aspects failed miserably.
It’s because people do not understand what ecommerce technical discovery is. What are this phase’s goals, and what the expected outcomes are.
This often leads to another problem. Ecommerce technical discovery sessions need more structure and agenda. No matter whether it is a new greenfield implementation or ecommerce migration.
They are treated as loose technical conversations. They often end with jumping from one topic to another.
This brings chaos and makes most participants confused and stop following the conversation.
Which may be the nail in the coffin of the whole ecommerce technical discovery phase.
Especially now when a lot of sessions are remote.
But there are other problems.
Talking mainly about technology can make the client feel uncomfortable. Technology is complicated and may not be well understood by everyone. This can make the client think the team needs to understand the business.
And this is the easiest way to put your ecommerce project on hold.
After participating in many technical discovery sessions for ecommerce, I have identified a few simple things. You can do these things to increase the success rate of discovery sessions.
What Is the Goal Of Ecommerce Technical Discovery?
The primary goal of the ecommerce technical discovery phase is to lay a solid foundation for the ecommerce project. It aims to ensure that the project is planned and executed to meet the client’s business objectives, stays within budget, and is delivered on time.
To do it, you will need to:
- Definite the real problem the customer is trying to solve,
- Understand the client’s pain points and frustrations,
- Understand everything that isn’t working for the client.
That is why you can’t focus only on the technology aspect.
You must understand the business problems to identify “the real problem”.
I call it “the real problem” because sometimes the problem may ultimately differ from what the customer thinks. You can identify it only through business conversations.
Some may say: “We talked about it many times during the sales cycle. We don’t need to discuss it again”.
We aim to take them to a more detailed level that we haven’t discussed in earlier phases.
Not to repeat them.
The Ecommerce technical discovery phase should consist of the following:
- Meeting sessions – when you talk. Those can be business discussions or technical discussions. Your primary goal should be to ask the right questions. Listen to answers and write down the information,
- Analysis time – when you aggregate all the information and build the bigger picture.
Meeting sessions should be organized around topic areas.
For example, you have a session discussing “Pricing, Taxes and Discounts” or “Fulfillment and Order Management”.
Each session should have a clearly defined agenda to share with invited people beforehand.
The “Pricing, Taxes, and Discounts” main points could be:
- Price Strategy and Management,
- Tax Rules and Calculations,
- Sales and Discounts.
This approach ensures that the right stakeholders are invited to participate. It also helps to make sure people are prepared for the meeting. And most importantly, it ensures the client is in good hands.
The biggest mistake many teams make is not organizing sessions around topic areas.
Or if they do it, they don’t create an agenda to follow.
Why is it a problem?
People quickly move from one topic to another when the discussion is not adequately facilitated. This causes chaos and a lack of progress.
People spend hours talking and do not reach any conclusions.
5 Steps Of Successful Ecommerce Technical Discovery Phase
Ecommerce technical discovery sessions are not the time when teams build the solution.
It is the time when teams should understand the problems and validate assumptions.
Those should be translated into a solution blueprint during the analysis time.
If the team needs to validate the solution or discuss technical details, they should organize a dedicated session with the technical team.
I took part in many ecommerce technical discovery phases. Some of them failed, ending with no project. Some turned into ecommerce implementation projects.
Most successful discovery phases followed the following steps:
1) Identify The Scope Of Ecommerce Technical Discovery
Some discovery sessions can be split between various teams. Or the scope of the discovery phase can be limited. It becomes more common once clients implement Composable Commerce solutions. Or conduct Composable Commerce Migration.
Ensure you plan required sessions and understand who owns each.
Discuss and agree on deliverables that are supposed to be produced after technical discovery is over. It can be, for example, a project scope, project budget, project plan, solution blueprint, architecture diagram, backlog of tasks, etc. Or any combination of them.
2) Create And Distribute The Schedule
Identify dependencies between sessions. Also, identify dependencies between other external activities. These dependencies impact your ecommerce technical discovery process. This will help you to create the correct order in your schedule.
Plan one or most of two sessions a day. Make the session at most 90 minutes. This is usually the longest time to hold participants’ attention.
Make sure you have enough time left for the analysis part.
Ensure each session has a proper audience invited for the meeting. If the session is about marketing, invite everyone involved in marketing processes.
The key is to have quick access to the information and decision-makers.
Remember to plan a few placeholder session slots for follow-up discussion. Those are always needed to finish open conversations.
Most importantly, the schedule should have defined the beginning and end of the discovery phase. It should also indicate the client’s expected date to decide on implementation.
3) Lead the Discovery Sessions Following the Prepared Agenda
Make sure conversations stick to points described in the plan.
Keep other topics from taking over. If the topic is planned for another session, please mention it and bring the discussion back on the original track.
If it is an extra topic, plan the conversion for one of the placeholder sessions.
You aim to collect and confirm as much information as possible. You also aim to have all the necessary people in the meeting.
4) Analyze And Prepare Deliverables
Make sure you have enough time to gather and understand all the information collected during discovery sessions. You can partially do it between sessions.
Once all sessions are over, finish artifacts that must be delivered to the customer.
5) Review Documents With The Customer
Once you deliver documents to the client, give some time for review.
Organize another meeting where the client will have a chance to ask questions and raise any concerns.
Confirm the date again when your client will provide feedback and make a decision about the ecommerce implementation project.
Everything You Need To Know About Ecommerce Technical Discovery
The ecommerce technical discovery phase plays several crucial roles in ecommerce projects. It helps to:
- Identify potential challenges and risks early. Then, you can take proactive measures to mitigate them,
- Understand the project scope, expectations, and deliverables by all project stakeholders,
- Ensure human and technical resources are allocated and utilized effectively,
- Align project outcomes with customer expectations and increase customer satisfaction.
Ecommerce Technical Discovery Can Be Very Short Or Long
The ecommerce technical discovery phase may take different forms. It depends on the project’s size. It may also involve many parties.
Small businesses and individuals who want to create an ecommerce store may need a Business Owner and Consultant to build the store. Discovery can involve a few hours of phone conversation or face-to-face meetings. The two people discuss their needs and agree on a plan.
In the case of big enterprise ecommerce projects, the list of the project stakeholders is usually much longer. It often involves a system integration company (SI) with the know-how to implement it. It also includes technology vendor representatives (a company selling an ecommerce product) and the client.
Members of many departments represent the client. They are involved in ecommerce processes or use an ecommerce platform. In this case, the ecommerce technical discovery phase may take the form of many meetings. It can last a few weeks.
Ecommerce Technical Discovery Outcome
The ecommerce technical discovery phase aims to lay a solid foundation for the ecommerce project.
It is the critical step after which the client implements ecommerce.
After this step, all the teams should have clarity regarding the following points:
- Scope – a clear list of items that will be implemented as part of the project,
- Project plan – initial version of project plan presenting anticipated start and end date of ecommerce implementation,
- Solution blueprint – high-level design of the system that will be implemented during the ecommerce project,
- Project budget – the overall cost of the project,
- Responsibility matrix – a clear understanding of the area of responsibility for each party involved in the project.
Those should be typical outcomes from the ecommerce technical discovery phase.
This is the minimum required to help customers decide on an ecommerce implementation project.
The Key to Successful Ecommerce Technical Discovery
All of the above can help increase the success rate of the ecommerce technical discovery phase.
But how do you get better at applying those points? How do you convince the client to stick to your plan?
Make it a process. Process with well-defined steps and defined outcomes.
Discuss them with the client beforehand. Explain the reasons and benefits of this approach.
If you lead the ecommerce technical discovery phase, the client will trust you to know what you are doing.
Remember:
- Identify the scope of your technical discovery phase and expected deliverables.
- Create a schedule and agenda for each session.
- Don’t talk only about technology. Keep a healthy balance of business and technical discussions.
If you want to master ecommerce projects, start with ecommerce technical discovery.
This is the foundation for your success.
