Skip to content


"Building" an EKG-based use case involves everything from detailed requirements gathering---structured around the Use Case Tree---all the way up to delivery of components for your production EKG-platform.


In general, for most use cases, there is very little actual coding (or "building") involved since the majority of use cases can be done in a ”low-code” or even ”no-code” manner by specifying all details of all functional requirements in the context of the UCT which then all ends up as ”executable models” in the EKG itself. Most of the actual "building" of the use case consists of adding more detail to the use case at hand. Capturing more knowledge about it. Once enough detail has been specified, it runs, job done.

  • Allocate

    Allocate resources, organize a team and start creating a "Center of Excellence for the EKG" (CoE).

    Learn more

  • Design


    Learn more

  • Implement

    Detail the use case

    Learn more

  • Test

    Add test scenarios, deliver full coverage

    Learn more

  • Verify

    Verify with the business

    Learn more

  • Deliver

    Continuously improve, deliver small increments frequently

    Learn more

To set up for success, it is essential that the build phase starts with the following artifacts and results that are created during the plan phase are input for the build phase:

  • From Envision: A shared vision and strategy, an agreed overall scope and direction, all stakeholders are identified and are supporting the strategy.
  • From Discover: The UCT, a broad-stroke overview of all use cases in the agreed scope with agreed names and "Business Outcomes" plus abstract business descriptions of functional requirements. (Details of the UCT to be determined during the build phase).
  • From Assess: A light assessment of the various non-functional requirements and levels of maturity in the areas of the organization that the EKG and the EKG team would depend on plus a plan as to how to bridge gaps.
  • From Train: Depending on the size of the selected use cases and their scope, everyone involved should have gone through some light basic training where the various new concepts around EKG have been explained, especially the members of the initial team.
  • From Chart: An agreed, supported and funded project plan. With a well-defined definition of done (DoD) or a definition of what a successful delivery of the selected use cases means, ideally around agreed business outcomes.
  1. Creating an EKG can only be successful if it is done as part of the company’s strategy with solid top-down support and leadership.
  2. Bottom-up development of just one Knowledge Graph Use Case will only lead to "yet another silo (YAS)" and cannot realistically compete with existing technology stacks, missing out on the actual benefits that EKG can provide.
  3. An EKG requires internal ownership and a team that understands the many new paradigms that are involved.
    • Creating a solid team---let's call it the Center of Excellence (CoE) for the EKG---is essential.
    • It is not the technology that holds us back---the technology works---it is the internal organization’s readiness and level of maturity in a number of areas that require focus. Perform a solid maturity assessment.
  4. A structured method is required that covers all areas, from strategy and idea inception to capturing the right business outcomes and requirements all the way to delivering a use case in production and supporting it during its life cycle.
  5. Any investment in a properly executed plan phase will drastically increase the likelihood of successful delivery.
Author: Jacobus Geluk