Technical (Customer) Project Coordination

Delegator

Role Customer (Key) Account Manager

Role Keepers

Open, New Employee

Contact

#sol Team Chat

This is a new role. We’ll further clarify this role during onboarding.

Purpose

Why is this role needed, what need of the organization does it address, or how is it relevant within the organization?

Once a Solution Architect has understood the requirements, drafted and quoted a solution with Sales, and this has been ordered, the Account Managers serve as a tactical and strategic interface to our customers and coordinate projects and later escalations that go beyond individual requests (tickets). Projects are often quite extensive and technically complex, especially during onboarding or when a customer needs extensions/changes. We also often have inquiries (tickets) that are technically and commercially complex, and we sometimes have internally driven changes affecting multiple customers or internal process improvements that could benefit from clear ownership.

We therefore see the need for the Account Managers to have a technical (customer) project and service management capacity that can drive projects and changes forward, take over coordination, handle technically complex customer escalations, join customer meetings to better understand requirements, and similar tasks. This will relieve the Solution Architects and Account Managers and make orders (tickets) clearer for the Value Stream Team Engineers.

Key Responsibilities

List the essential responsibilities assigned to this role.

  • Coordination of technical customer setup or change projects

  • Support through high-level technical understanding and driving clarifications

  • Project and process change ownership for service delivery and support processes

  • Support technical customer escalations and follow-up on relevant incidents

Stakeholders and Key Deliverables

Whom does this role deliver value to, what do they need from this role?

VSHN Value Stream Teams
  • Ownership and clarification of technically complex customer requests into refined tasks/epics.

  • Representation of customer’s needs and feedback during the project or escalations/bigger incident follow-ups.

Customer Account Managers
  • Support in technically complex matters with their customers.

  • Support in incident coordination and follow-ups.

  • Technical coordination of inside-out (product)-driven changes affecting their customers.

VSHN Customer
  • Technical coordination of their onboarding or change projects.

  • A working request handling and support process according to SLA and best effort customer service.

Project Management and Product Owners
  • Inside-out driven initiatives to align existing customers' setups to product strategy.

Dependencies

Customer Account Managers

They own the overall customers, including onboarding or change projects. This role supports with more technical understanding and coordination of the technical tasks to deliver. This is important to avoid becoming the sole go-to person for the customer and a potential single point of failure or bottleneck.

Value Stream Teams
  • They need to help the role keep up with the technical knowledge, give insights into how things work, provide hands-on support, and teach about tech and VSHN products and services.

  • They need to help document existing solutions, as they might have the best understanding at the moment, while this role can ensure and coordinate how this needs to be done.

  • Triage of (complicated) clear requests needs to work, so that the Account Managers and this role can focus on the technically, strategically, or commercially complex cases.

Competencies, Qualities, and Skills

  • Business mindset, tactical and strategic thinking

  • Strong technical background (software/devops), broad is more important than deep understanding

  • Customer service-oriented

  • Cooperative leadership personality, not a one-man show

  • Curiosity to learn and understand technically complex situations, new products, and technology

  • Process and workflow thinking, striving to clarify, automate, standardize, and structure things

Assignment of this Role

  • We would start this role as an experiment, for example, for 3-4 months and define clear goals/evaluation criteria. The experiment should prove that this need a) exists and b) can be covered by such a role. We might set priorities on what to focus on first, as we don’t see it as realistic that all of this role can be done right from the start.

  • We try to hire/contract a person with a strong technical background and the competencies mentioned above.