๐ข๐ฟ๐ฐ๐ต๐ฒ๐๐๐ฟ๐ฎ๐๐ถ๐ป๐ด ๐๐ฒ๐๐ถ๐ด๐ป ๐๐ผ ๐๐ผ๐ป๐ณ๐ถ๐ด ๐ถ๐ป ๐๐ต๐ฒ ๐ฆ๐๐๐: ๐ ๐ฃ๐ฟ๐ฎ๐ฐ๐๐ถ๐ฐ๐ฎ๐น ๐๐ ๐ฎ๐บ๐ฝ๐น๐ฒ
Most delivery teams still spend too much time translating and rewriting what already exists. This post walks through a practical โdesign to configโ approach, where inputs are orchestrated through a set of agents to produce structured, build-ready outputs. Itโs not about replacing peopleโitโs about shifting effort from creating artefacts to reviewing and governing them. The result is cleaner handoffs, earlier visibility of gaps, and a more controlled path from requirements to build. The real shift isnโt automation. Itโs moving work leftโso design, validation, and alignment happen before the build even starts.
Dawn Thiart
4/5/20261 min read
(creating artefacts โ orchestrating outcomes)
Think of it as a small agentic delivery system โ not a single agent.
๐ญ. ๐๐ป๐ฝ๐๐๐ ๐ฐ๐ผ๐บ๐ฒ ๐ถ๐ป
โข approved requirements
โข workshop transcripts
โข templates and design patterns
โข data models and integration standards
These already exist โ but are spread across documents and notes.
๐ฎ. ๐ข๐ฟ๐ฐ๐ต๐ฒ๐๐๐ฟ๐ฎ๐๐ผ๐ฟ ๐๐ด๐ฒ๐ป๐ (๐ฐ๐ผ๐ป๐๐ฟ๐ผ๐น ๐น๐ฎ๐๐ฒ๐ฟ)
Its role is to:
โข understand the request
โข select the right agents
โข sequence the work
โข consolidate outputs
โข route exceptions to human review
๐ฏ. ๐ฆ๐ฝ๐ฒ๐ฐ๐ถ๐ฎ๐น๐ถ๐๐ ๐ฎ๐ด๐ฒ๐ป๐๐
๐ฅ๐ฒ๐พ๐๐ถ๐ฟ๐ฒ๐บ๐ฒ๐ป๐๐ ๐๐ด๐ฒ๐ป๐
โ converts requirements into config intent
๐ฃ๐ฎ๐๐๐ฒ๐ฟ๐ป ๐๐ด๐ฒ๐ป๐
โ maps to standard patterns:
โข Outlook integration
โข account/contact/opportunity model
โข business rules
โข F&O field integration
โข approval workflows
๐๐ผ๐ป๐ณ๐ถ๐ด ๐๐ด๐ฒ๐ป๐
โ generates draft config items:
โข integration field mapping
โข business rules
โข security roles
โข approval flows
โข BPF stage logic
โข Outlook/email config
๐ฉ๐ฎ๐น๐ถ๐ฑ๐ฎ๐๐ถ๐ผ๐ป ๐๐ด๐ฒ๐ป๐
โ identifies gaps, conflicts, assumptions, dependencies
๐๐ฒ๐น๐ถ๐๐ฒ๐ฟ๐ ๐๐ด๐ฒ๐ป๐
โ produces build-ready config tickets
๐ฐ. ๐๐๐บ๐ฎ๐ป ๐ฟ๐ฒ๐๐ถ๐ฒ๐
โข Solution Architect โ design integrity
โข Functional Lead โ business accuracy
โข Technical Lead (if required)
This step ensures control โ not uncontrolled automation.
๐ฑ. ๐ข๐๐๐ฝ๐๐๐
โข standard + custom config items
โข open questions and assumptions
โข dependencies and actions
โข build-ready tickets
โข traceability to requirements
๐ช๐ต๐ฎ๐ ๐๐ต๐ถ๐ณ๐-๐น๐ฒ๐ณ๐ ๐น๐ผ๐ผ๐ธ๐ ๐น๐ถ๐ธ๐ฒ
๐ง๐ผ๐ฑ๐ฎ๐
โข interpret requirements
โข map patterns manually
โข write config from scratch
โข resolve gaps late
๐ช๐ถ๐๐ต ๐๐ต๐ถ๐ ๐บ๐ผ๐ฑ๐ฒ๐น
โข orchestrated flow
โข generated draft outputs
โข review replaces creation
The shift
๐ฆ๐ผ๐น๐๐๐ถ๐ผ๐ป ๐๐ฟ๐ฐ๐ต๐ถ๐๐ฒ๐ฐ๐
write design โ govern outputs
๐๐๐ป๐ฐ๐๐ถ๐ผ๐ป๐ฎ๐น ๐๐ฒ๐ฎ๐ฑ
translate requirements โ validate structure
๐ง๐ฒ๐ฐ๐ต๐ป๐ถ๐ฐ๐ฎ๐น ๐ง๐ฒ๐ฎ๐บ
interpret design โ build from standardised config