Use this article to name your Ingrid implementation team: the six roles your team needs, what each role has to be able to do, and who Ingrid brings to the project.
This article is for retailers preparing an Ingrid implementation, especially project sponsors and project leads. The team you name is the single biggest predictor of your Ingrid go-live date, more than your platform, your carrier mix or the number of markets you launch.
One person can cover several roles, and an agency can fill them. What matters is that every role has a clear owner from day one, and that the owner has the time and the authority the role needs.
The six roles in an Ingrid implementation team
The table below shows the six roles your Ingrid implementation team needs, what each role does, and what each role needs:
Role | What they do | What the role needs |
Project lead | Runs the day-to-day cadence with your Ingrid lead. Your single point of accountability. | Senior project management experience, ideally on a delivery or commerce program. |
Technical lead | Owns your integrations to Ingrid: your e-commerce storefront, plus your WMS (warehouse management system) or ERP (enterprise resource planning) system where those are in scope. | Knows your tech stack end to end. Available weekly, not occasionally. |
Decision-maker | Resolves scope, carrier and rollout questions within one working week. | The mandate to decide without escalating. |
Ingrid administrator | Owns Ingrid in your operations after go-live. Trains during configuration. | An operations background, knows your delivery logic, comfortable with rule logic. |
Testing lead | Leads testing with named testers, agreed early. | Knows your delivery logic, your common flows and your edge cases. Can write real test scenarios. |
Project sponsor | Unblocks resourcing and competing priorities. Joins steering meetings. | A senior leader with a delivery, digital or operations remit. |
Two Ingrid implementation roles worth naming early
The decision-maker. The "within one working week" part is the whole point. Ingrid implementations rarely stall on hard problems; they stall on straightforward questions waiting on someone who is in a different meeting. If your decision-maker needs to escalate every carrier or scope decision, the escalation path is the real timeline.
The Ingrid administrator. The Ingrid administrator is the one role that outlasts the implementation. The Ingrid administrator trains during configuration, so that when your Ingrid implementation consultant hands over, your delivery logic is owned by someone in your own team who can change it without a support ticket. Naming the Ingrid administrator late means training them late, which means depending on Ingrid for changes you could be making yourself.
Who Ingrid brings to your implementation
Ingrid staffs every implementation with an implementation consultant, and adds project management and integration support where the scope calls for it.
Your Ingrid implementation consultant runs the project with you from scoping through go-live, then stays alongside you during hypercare before the Ingrid Customer Success and Support teams take over.
Related
Implementation: the five phases of an Ingrid implementation