Services of the Chengdu orchid desk

Six ways to tend an integrated system

SPIKE

Bloom sheets, spike notes and collector letters run from the Chengdu orchid desk of ChengDu QiaChiLan Network Technology Co., Ltd., and every service below is a station along that same rail. Read the catalogue, or start a conversation with the desk whenever you are ready to open a season.

Book a spike window with our Chengdu desk

The catalogue in brief

ChengDu QiaChiLan Network Technology Co., Ltd. offers six connected services that carry a system from first observation to a live and understood installation. They are not separate packages sold at separate prices; they are stations along a single rail, and most engagements move through all six in a natural order. Some clients begin midway when they already know their organisation well, and some return for a single station after a system has already been established.

ChengDu QiaChiLan Network Technology Co., Ltd. opens its spike window for the coming season, inviting new teams to step into the gallery.

Bloom Sheet Bays

A bloom sheet bay is where every engagement begins. The bay is a working station in which we lay out the people, tools, data and decision points of an organisation onto a single large sheet. Nothing is assumed and nothing is hidden; the sheet is drawn in plain sight, with the client team beside us, so that gaps become visible before they become costs. We ask where work waits, who holds the knowledge, and which connections are carried in a person head rather than in a durable record.

When the sheet is complete it reads like a map of an orchid house: each room, each rail and each watering line has its place, and the movement between them is clear. Teams often tell us that the bay alone changes the conversation, because for the first time everyone sees the same picture. The bloom sheet then becomes the reference against which every later decision is measured, and it is revised whenever the organisation genuinely changes.

Spike Note Runs

A spike note run converts the observations of the bay into a numbered trail of short, plain notes. Each note holds one condition, one risk or one opportunity, and each is worded so that a reader who was not in the room can understand it. The notes are kept deliberately small; a note that needs three paragraphs usually hides a disagreement that should be surfaced in a collector letter instead.

Runs are written quickly and reviewed in sequence, which keeps the language honest. Engineers and owners read the same trail, and the trail survives staff changes because it lives in a shared record with dates and owners attached. By the end of a run the team has a working list of what must be protected, what must be replaced and what can safely be left alone, and the design has something factual to lean on.

Collector Letter Desks

The collector letter desk is our writing room. Here we draft the briefs, approvals and handover notes that travel between owners, engineers and support staff. Every letter is short, specific and dated, and every letter names the decision it records so that nobody has to reconstruct the reasoning from memory months later.

Letters are collected into a single library for the engagement. That library becomes the spine of the project: it holds the scope that was agreed, the changes that were approved, the risks that were accepted and the questions that remain open. When a new engineer joins midway, they read the collector letters first and understand the design without needing a long briefing call.

Spike Windows

A spike window is a scheduled build span in which we assemble one vertical slice of a system end to end. A window might connect a scanner to an inventory service, migrate a shared drive into a governed store, or replace a fragile export with a monitored interface. The scope is narrow on purpose: each window finishes with something that can be tested, demonstrated and rolled back if it misbehaves.

Windows are measured in days rather than quarters, and every window begins with a short plan and ends with a short record. Because the slices are small, mistakes surface early and corrections stay cheap. Owners can approve each window in plain language, and the overall system grows the way an orchid spike grows, one node at a time, each node stronger than the one before it.

Mist Review Rounds

Mist review rounds are light, frequent checks that keep a project nourished between major milestones. In each round we look together at logs, diagrams and live behaviour, then correct course while corrections are still inexpensive. The rounds are short by design, so they do not become another meeting that people learn to avoid.

Over a season the rounds build a steady rhythm that teams come to rely on. Problems are named early, small improvements are folded into the next window, and the shared record grows month by month. The result is a system that is watched rather than merely installed, and a client team that understands it well enough to raise a concern before it becomes an outage.

Gallery Sittings

A gallery sitting is the closing session in which we walk a client team through the finished system as though it were an exhibition. Handover is a guided tour, not a folder of files. We show each part, explain why it was built the way it was, and hand over the bloom sheet, the collector letters and the review schedule in good order.

The sitting is also a starting point. Support arrangements, named contacts and the first mist review rounds of the new season are agreed during the sitting, so the system does not fall silent the moment the engagement formally ends. Many clients return for a second sitting a year later, walking the same gallery with fresh eyes and a new season of growth ahead.

How a season runs

Most engagements follow one calm arc. We begin with a short conversation to understand your organisation and your appetite for change. A bloom sheet bay follows, then a run of spike notes, then a set of collector letters that fix the direction in writing. From there the work proceeds window by window, with mist review rounds keeping the whole programme honest. The season closes with a gallery sitting and a clear schedule for the months that follow.

Nothing about this arc is rigid. Some clients need only a bloom sheet and a handful of notes; others begin at the window stage because their direction is already settled. The desk adapts the arc to the work, never the other way around.

What shapes the arc

  • The size and pace of your daily operations
  • How much of the current system is documented
  • Where your data lives and who guards it
  • How quickly decisions can be approved
  • The support rhythm you can sustain after handover

Bring your next system to the gallery

If your team is planning a new integrated system, repairing one that has grown unruly, or simply wants a clearer view of how the work already moves, the Chengdu orchid desk is ready to help. Write to bloom@swiftorchid.buzz, call +17755930358, or use the contact form to open a spike window for your own season.

Open the contact desk and start a conversation