Short notes from recent work

Logistics member portal sequencing

“They refused to invent a greenfield fantasy. The rebuild sequence named which modules stay, which retire, and who owns each cutover weekend. We still argue about priorities, but at least the arguments use the same map.”

— Mei-Ling Hsu, portal programme lead

Municipal services architecture review

“The architecture review was slower than our previous vendor’s workshop, and that was the point. We finally had a diagram the ops team trusted. I would have preferred clearer language on vendor lock-in earlier in week one.”

— Daniel Chen, IT director

Partner extranet cutover readiness

“Their readiness scorecard caught a missing partner notification path two weeks before freeze. That alone paid for the review. The report was blunt about our thin on-call coverage.”

— Aron Wu, operations manager

Extended story: partner portal rebuild plan

A mid-size distributor in northern Taiwan asked App Brook Base to plan a rebuild of a partner extranet that still depended on a decade-old order form service. Discovery showed three teams believed they owned pricing rules. The rebuild plan did not start with a visual refresh. It started by assigning a single pricing owner, retiring two shadow spreadsheets, and sequencing identity changes before catalogue work.

The sponsor accepted a narrower first release than marketing had hoped for. Support tickets related to incorrect partner pricing dropped after the first cutover. The full catalogue redesign remained on a later stage with its own estimate.

Extended story: internal service desk platform

An agency-led rebuild had stalled after wireframes. App Brook Base ran an Architecture Assessment, then a short Portal Rebuild Planning follow-on. The key finding was that ticket routing rules lived in three places. The roadmap forced a consolidation decision before any new intake screens. Delivery resumed with the agency still building screens, but against a written sequence the client could audit.