As president and financial advisor at Thimbleberry Financial, Amy Walls leads a team of financial experts who help clients manage and grow their money for a purpose.

Having standard processes is integral to an organization’s success. So Amy created business processes in Microsoft Word documents to enhance their operations. However, her team had difficulty accessing the information they needed to perform their tasks.

When Amy’s business coach recommended SweetProcess, a workflow documentation software, she was reluctant to use it at first. But her reluctance soon changed to excitement. In this case study, Amy talks about how SweetProcess has helped her grow a more efficient team and streamline the operations at Thimbleberry Financial.

Amy Walls, President and Financial Advisor at Thimbleberry Financial

About Thimbleberry Financial

Thimbleberry Financial is a financial planning and wealth management institution in Portland, Oregon. It offers clients valuable advice to help them achieve their financial goals in the most efficient ways.

The team at Thimbleberry Financial prioritizes its relationship with clients to fully understand their needs and provide custom services to meet those needs.

Inspired by the local thimbleberry fruit that appeals to its immediate community, the organization takes pride in servicing its local community for the best results.

Listen to the audio interview

Listen to more expert interviews like this

The Pitfalls of Ineffective Documentation

As a financial advisor, Amy had mastered the art of creating effective operations manuals for her business. Her document was shared as a good example in her business training group. With such success, she assumed that the processes she outlined in Microsoft Word documents were clear enough to be used by her team members, but that wasn’t the case. They abandoned the documents and did things their own way.

“It wasn’t clear. When people wrote what they did, they wrote it differently, and then people had a hard time following it. You couldn’t check anything off,” Amy laments.

The realities of ineffective documentation became more glaring when the organization started having turnover. Team members couldn’t keep track of their activities.

“We were having quite a bit of turnover and that turnover had to do with a couple of things. One, our team being so small, was wearing too many hats. I’m keeping track of what I have to do with this work, but then I have a whole other hat over here that has a different body of work. Not having an easy reference for what had to happen made that hard,

Get the future of podcasts.