Back to Past Projects Overview
Table of Contents
The Start of Systems thinking – Some jobs stretch you in unexpected directions. You’re hired for one thing, but end up wearing five hats—and somewhere in the middle, you realize you’re building more than just tasks. You’re building systems.
That’s what happened during my time at Outreach North America (ARP denomination). It started with admin work—but quickly became one of the most formative roles of my early career.
Outreach North America (early 2000s)
I was hired as an administrative assistant, primarily to help with donations for a capital fundraising campaign. But I quickly saw room for improvement—and proposed a better donation tracking system. I wrote and submitted a formal proposal, and it was approved. That small win taught me that systems could evolve—and I could help lead that evolution.
From there, the role expanded.
I redesigned their website using Dreamweaver, updated events and contact info, and even created a new logo. I was also gaining experience with tools like Photoshop and Illustrator, which opened up new design possibilities.
Beyond the website, I helped compile statistical data from printed materials into organized databases. That info guided church planting strategy, giving the director real insights into where and how to grow. I also helped coordinate events for new church planters, including working with teams going through the organization’s assessment program.
One standout experience: I was involved in searching for, and meeting with, videographers to produce a promotional video for the organization. It was my first exposure to managing a creative project that wasn’t just web-based, and it expanded how I saw my own skill set.
What I’d Do Differently Today
• Build the site using WordPress with donor tracking and CRM integration
• Create dashboards for donor data and church planting trends
• Use AI to surface insights, summarize data, and help train new planters with better content
• Create evergreen blog-style updates and use a content calendar to unify messaging
• Offer structured templates and onboarding tools to reduce dependency on outside consultants
The Takeaway
Looking back, I was thinking in systems before I had the words for it. I was:
• Building workflows without formal training
• Creating documentation because it made sense
• Connecting teams and tools across departments
• Finding patterns in messy data that could lead to real decisions
It was also a reminder that roles change—and when you step up, you often discover skills you didn’t know you had.
Coming up next: Day 4 – The Side Gig That Should’ve Stayed on the Side (SpinningSilk Multimedia)