Turning 22-Month Website Delivery into a Repeatable 2–3 Month System
I redesigned a fragmented Farm Credit website-delivery process into a parallel, reusable system that cut the full discovery-to-launch lifecycle from roughly 22 months to 2–3 months on the first site, expanded team capacity, and supported at least eight distinct association launches.
When I joined the team as a Senior Software Engineer, a new Farm Credit association website typically took around 22 months from initial concept through launch. That timeline was not caused by a lack of effort. Every association had its own identity, content, relationship context, accessibility needs, and compliance requirements. The problem was the delivery system: work moved through long handoffs, development depended heavily on an offshore Kentico queue, and an unfriendly CMS made iteration difficult for nearly everyone involved. A conversation with designer Chris about the concept-to-launch timeline helped bring the bottleneck into focus. We looked at what was taking so long and what could be streamlined without sacrificing the individuality of the finished websites. I was given room to try a different approach.
The transformation at a glance
Custom websites, delivered through a system the whole team could use
01 · Delivery speed
From a 22-month relay race to a 2–3 month parallel lifecycle
Before · sequential handoffs
- Discovery
- Design
- Content
- Offshore queue
- Review and rework
- Launch
Every stage waited for the baton.
After · coordinated workstreams
The first site proved the model immediately.
02 · Parallel delivery
The team worked together instead of waiting on final handoffs
Misfires were corrected during delivery—not discovered at the end.
03 · Reusable foundation
The websites stayed distinct while the delivery system became repeatable
Consistency where it helped. Flexibility where identity mattered.
Reusable Kentico foundation
04 · Team capacity
Knowledge moved from one person’s head into a durable team capability
- 01Learn the platformBring Kentico and frontend integration capability in-house.
- 02Pair and documentMake the workflow visible, reusable, and teachable.
- 03Share ownershipTwo engineers independently lead sites while supporting each other.
- 04Scale the systemTwo sites move in parallel and broader strategic work becomes possible.
Expertise becomes more valuable when it stops living in one person’s head.
The impact path
Inherited
A custom association website typically took roughly 22 months from initial concept through launch.
Owned
After a conversation with designer Chris about the concept-to-launch timeline, I recognized the delivery bottleneck and identified where work could be streamlined.
Changed
I began each project with shared discovery involving the association relationship manager, designer, content specialist, and me.
Result
22 months → 2–3 months — Full discovery-to-launch lifecycle
What I inherited
The problem and the reality around it
The problem
- A custom association website typically took roughly 22 months from initial concept through launch.
- Delivery moved through slow handoffs between discovery, design, content, and an offshore development queue.
- Each association still needed its own branding, content, culture, accessibility requirements, compliance requirements, and relationship context.
- Kentico was not user-friendly, creating friction for both implementation and ongoing content work.
The constraints
- The solution could not flatten distinct association websites into generic templates.
- Design, content, technical scaffolding, implementation, responsive behavior, and review all had to remain coordinated as the work evolved.
- Accessibility and compliance needs varied by association and initially had to be translated into the implementation directly.
- The delivery system had to work within Kentico rather than replacing the CMS.
What I owned
My responsibility in the work
After a conversation with designer Chris about the concept-to-launch timeline, I recognized the delivery bottleneck and identified where work could be streamlined.
I redesigned the workflow so relationship management, design, content, and development could move in parallel instead of waiting on final handoffs.
I learned Kentico, brought JavaScript and frontend integration work in-house, and built reusable CMS foundations using Kentico, JavaScript, HTML, and CSS.
I created the process documentation and helped turn workshop-style knowledge sharing into reusable onboarding and association training material.
I transferred the Kentico delivery process to an experienced engineer through pairing so he could independently own association sites.
How I approached it
Decisions, tradeoffs, and delivery
I replaced sequential handoffs with a parallel, iterative workflow. Discovery brought the association relationship manager, design, content, and development together at the beginning. While design and content shaped the association-specific visual direction and copy, I built wireframes, scaffolding, and the initial Kentico structure. I integrated designs as they became ready, worked with content to make sure layouts supported the material correctly, and handled responsive behavior throughout the build. Frequent reviews caught misunderstandings while they were still inexpensive to correct. Inside Kentico, I created reusable hero structures, callouts, content blocks, customizable components, and raw scaffolds. Those foundations standardized the avoidable work without standardizing the websites themselves.
- I began each project with shared discovery involving the association relationship manager, designer, content specialist, and me.
- While design and content developed the association-specific direction, I created wireframes, technical scaffolding, and the initial Kentico structure.
- I integrated design iterations as they became ready, worked with content to validate the layouts, and handled responsive behavior throughout implementation.
- I used frequent follow-up reviews to catch misunderstandings and misfires during delivery rather than at the end of a heavyweight launch phase.
- I created adaptable hero structures, callouts, content blocks, customizable components, and raw scaffolds inside Kentico so the delivery system could repeat while each website remained distinct.
- I paired closely with another engineer, supported shared code reviews and troubleshooting, and enabled two association websites to move forward in parallel without creating isolated silos.
- I initially helped train association staff to publish blog posts, create events, and build new content with widgets; the content team later took ownership of that training.
How I led
The team and stakeholder system
The strongest part of the work was the team around it. Design, content, relationship management, and development learned from one another instead of operating as isolated stages. I transferred the Kentico delivery process to an experienced engineer who had also been a mentor to me, primarily through pairing and showing him how the system worked. He ramped up quickly and could independently own association websites. At our busiest point, we each led one site while supporting the other through code reviews, troubleshooting, design and content questions, and launch checks. I also documented the process and initially helped train association staff to publish blog posts, create events, and build widget-based content without code. As the system matured, the content team took ownership of that training. The model became the formal standard through documented process, staffing and ownership changes, and the assignment of future association sites through the new approach.
Results
What changed
22 months → 2–3 months
Full discovery-to-launch lifecycle
The first website delivered through the new model moved from initial discovery to launch in roughly two to three months instead of the previous typical timeline of around 22 months. · Shared outcome
2 sites in parallel
Expanded delivery capacity
Once the Kentico process had been transferred, two engineers could each own an association site while continuing to support the other through reviews, troubleshooting, and launch checks. · Shared outcome
8+ websites
Repeatable model adopted
At least eight association websites were delivered through the repeatable system before I moved into broader strategic work. · Shared outcome
Leadership evidence
How I moved the people system
- — I recognized an operational bottleneck without waiting for a formal assignment and was trusted to test a better model directly.
- — I made the process visible, documented, reusable, and teachable so the capability could grow beyond one person.
- — I transferred the Kentico process through pairing and shared ownership, enabling another experienced engineer to lead sites independently.
- — I helped a cross-functional team preserve customization while gaining the structure needed to deliver consistently and independently.
Technical evidence
How I moved the product system
- — Reusable Kentico hero structures, callouts, content blocks, customizable components, and technical scaffolding.
- — Parallel design, content, frontend, CMS, and responsive implementation workflow.
- — Embedded iterative review that caught issues before launch rather than relying on a separate heavyweight gate.
- — Association staff enablement for blog posts, events, and widget-based content creation without code.
Technical footprint
Technologies and system areas
What I took from it
The lesson I carry forward
The first site using the new model reached launch in roughly two to three months, immediately proving that the full lifecycle could move dramatically faster without erasing what made each association distinct. The system helped clear backlog, take on more association work, reduce launch issues, improve teamwork, and create happier association partners. At least eight association websites were delivered through the model before I moved into broader work. The capacity it created also gave me room to focus on projects such as the Farm Credit Knowledgebase. I am proud of the speed and the reusable foundation, but I am proudest of the team growth. Expertise becomes more valuable when it stops living in one person’s head. By making a process visible, reusable, and teachable, individual skill becomes team capability. The goal is not to make everyone work exactly like you; it is to give people enough structure, context, and support to succeed independently.
Related work · Frontend