eNoble
Client 1
- Context: This is a client who we performed a custom build for.
- Challenge: Pick up a heavily customized project midway through the build. Most of the team had turned over in the previous weeks so we met each other and had to learn and work together to deliver this project on the fly.
- Role: Training Content Development Intern
- Actions: Delivered documentation and accompanying videos for custom business processes, assisted users with questions about Salesforce specifics.
- Outcome: We delivered a quality project on time and successfully led UAT and deployment. We have since performed another project on top of this build for the client to automate certain portions of repeat processes with the option to edit them while cloning.
- Lessons: My primary takeaway with this client is to trust what I know and to be curious about what I do not know. Now that I significantly understand their processes, I’m trying to gain a deeper knowledge of the zeroes and ones behind it all, and our dev team has been amazing in how they interact with me and willingly share their expertise.
Client 2
- Context: This is a client that we are on a success plan with. With a limited time and budget each month, we spend half of our time prioritizing features with the client and the other half of the time executing the plan.
- Challenge: Given time constraints, priorities that can change quickly given the course of their business, and a single point of contact, identify wins that can be quickly delivered to match their business needs and urgency in accomplishing them.
- Role: Jr. Solution Consultant
- Actions: Created formula to capture certain address information and return a county given certain items missing, Updated and created reports to account for incorrect fields, data quality, and disparate systems.
- Outcome: This is a solid working relationship that I anticipate continuing for the time being.
- Lessons: Be professional to the client, but be human with them. They’ll appreciate the humanity more often than not. Always be honest with them and provide context to the professional decisions that you make so you can guide the client towards that decisionmaking themselves!
Client 3
- Context: This was a client with both a primary project and a success plan.
- Challenge: Complete a build and supporting documentation for the client, who had plenty of other competing priorities and not a lot of time to devote to the project.
- Role: Training Content Development intern
- Actions: Built flow logic to automate some problematic processes.
- Outcome: The project fell through entirely.
- Lessons: Don’t stack all your eggs in one basket. If the client treats you like you are not the priority, there is a strong likelihood that you are not the priority.
Client 4
- Context: This was a project for a municipal client.
- Challenge: This was a two phase project where we needed to both deliver custom processes and inform the users about basic Salesforce capabilities.
- Role: Training Content Development Intern
- Actions: Created 36 written walkthrough guides and trained users on the system.
- Outcome: We successfully delivered this project on time.
- Lessons: I learned that I’m far better at public speaking than I used to be, especially when I operate within a system and constraints that I am curious about.
Client 5
- Context: This was also a project for a municipal client.
- Challenge: Given a quick turnaround, provide a quality build and documentation to a client
- Role: Training Content Development Intern
- Actions: Created documentation to support the build and the business processes, recorded videos for those who preferred spoken and live-click documentation
- Outcome: We met the deadline and I personally delivered approximately 10 pieces of documentation and their matching walkthrough videos.
- Lessons: Different teams have different energies in different situations, and that’s perfectly okay. It doesn’t impact the quality of the work.
Lenticular Solutions
Client 1
- Context: Salesforce data migration and data quality improvement work for active business use.
- Challenge: Ensure a smooth migration to a Salesforce org for a business that continues to scale.
- Role: Salesforce Admin / Consultant
- Actions: Supported migration and normalization of legacy records, applied standardization patterns to improve data reliability.
- Outcome: Reduced downstream friction caused by inconsistent data structures.
- Lessons: Don’t be afraid. Trust your team when you need guidance. Do your best and double check your work.
Ventana Consulting
Client 1
- Context: Deduplication and standardization services for a small insurance company.
- Challenge: Campaigns were spread out among duplicate contacts – needed to deduplicate the contacts and ensure that none of the campaign records were orphaned.
- Role: Salesforce Admin / Business Analyst
- Actions: Deduplicated contacts, reparented campaign records.
- Outcome: Successfully moved campaign records for hundreds of duplicate contacts and removed the extra contacts from the system.
- Lessons: Communicate, communicate, communicate, even if it seems like you’re yapping someone’s ear off. I’d rather be questioned for my confidence than to misunderstand a requirement, 100% of the time.
Mile High Dreamin’
Data Migration Project
- Context: Community event migration support in Salesforce environment.
- Challenge: Move from one Salesforce environment to another while not breaking existing integrations
- Role: Migration contributor
- Actions: Supported migration tasks tied to event-readiness needs, helped preserve data usability through transition.
- Outcome: The new org was delivered on time and with 100% accuracy in the integration
- Lessons: Always volunteer for things that will truly show what you know. This single project opened a lot of doors for me the last couple of years, and it’s all because I wanted to challenge myself. The other main takeaway was to trust myself and the process.
Chattanooga Symphony & Opera
Google Workspace Training
- Context: User enablement support for operational tooling and day-to-day productivity.
- Challenge: Teach people who are not traditionally technical how to take advantages of the features in the Google Workspace suite.
- Role: Trainer
- Actions: Delivered practical training guidance for target users, focused content on immediate usability and adoption.
- Outcome: Trained 5 users and improved confidence in day-to-day system usage through guided sessions, strengthened baseline capability for routine team workflows.
- Lessons: I don’t work well without a dialogue going back and forth. If I feel like I am talking to myself, I feel like the only person in a large room. For this reason, I’ve become much more frequent about encouraging back and forth communication.
Personal
Firestarter
- Context: Personal build and research initiative exploring how CRM systems can support creative and music-focused workflows
- Challenge: Create a system to unify the many moving parts of an indepedent musician’s life so they can spend more time connecting with the music and the people.
- Role: Builder and Researcher
- Actions: Defined initial project scope and architecture direction, mapped practical CRM use cases to creator-facing workflows.
- Outcome: Delivered an 80-page playbook for constructing a musical implementation.
- Lessons: There are a lot of moving parts to projects. You can’t control how many of those parts move, you can only how you control how harmoniously and consistently you choose to interact with the environment you are in. Essentially this project is very possible. The combination of time and funding is not. I’d love to pick this one back up.
Examining Music Taste Through Pivot Tables
- Context: Personal analytics project connecting long-term music data and storytelling.
- Challenge:
- Role: Analyst and project owner
- Actions: Structured music data for pivot-based analysis, developed interpretation patterns for insight storytelling.
- Outcome: Built a reusable analysis framework for music preference exploration, demonstrated intersection of data analysis and creative narrative.
- Lessons: This project was super fun, I just need to throw it in a Salesforce org and I’m on to something. I can really tell a story and I can hold an audience with a microphone.
Scout’s Bouts
- Context: Narrative-driven Salesforce learning project designed to improve retention and applied understanding.
- Challenge: Teaching my one year old how to run her pillow fight club through a Salesforce org.
- Role: Creator and builder
- Actions: Built structured learning artifacts around platform concepts, used recurring storytelling format to reinforce technical learning.
- Outcome: Improved concept retention and communication clarity, produced reusable educational content with consistent structure.
- Lessons: Always include your loved ones in your storytelling. It makes it ten times as fun, especially when art imitates life and vice versa.
Christopher Sauer 