Ivan Silva

Senior Product Manager · Enterprise B2B SaaS

All sixQuestion 02 of 06Admissions integration

One admissions system, several application schemes. One integration?

Full Fabric
Shipped ahead of plan, twice

Connecting an external admissions system to Full Fabric, then making one integration serve several application routes.

What was going on?

Universities received applications through an external admissions system. Without an integration, staff duplicated that data into Full Fabric by hand.

Why was it hard?

The application schemes were not alike, and each came with its own authentication requirements.

The integration had to work for more than one scheme, inside the same shared product instance.

What was mine?

Specification
I led the product specification and defined the requirements.
Sequencing
I sequenced the development work and coordinated it with engineering.
Acceptance
I managed acceptance of what was built.
Extension
I extended the solution to support multiple application schemes and helped make it reusable.

What shipped?

Two related integration releases, each delivered ahead of its planned date.

The capability supports different admissions routes within one shared product instance.

What does this show?

  • Enterprise integration strategy
  • API-oriented product thinking
  • Authentication requirements
  • Requirements decomposition
  • Delivery with engineering
  • Extensible workflow design