About us
After 6+ years working with KnowledgeOwl, I kept having what I called "best practice" calls with customers: conversations that weren't about the software, but about what the best, fastest, or most maintainable ways to achieve their goals were. We often unwound decisions they didn't know they'd made about the processes they used.
I realized that I was advising on the process of knowledge management, rather than the software or the content. And I enjoyed it.
And so, knowledge with sass was born.
Kate Mueller (a.k.a. Sassafras), Owner
I have a widely varied background: I have an M.A. in English and I spent several years teaching college-level writing. Like many adjunct instructors, I got burnt out. So I took a job in a temp call center for a broadcasting company. That led me into Microsoft Access database design and my first technical writing.
When I realized how much I enjoyed databases and software, I went back to school for an M.S. in Information Management. From there, I worked in financial services and for several small- to mid-sized software companies. Along the way, I've written technical documentation, manually tested software, done technical/product support, helped with content marketing, and sometimes managed product.
My strengths lie in process-focused changes, creating a culture that prioritizes knowledge management and sharing, and an at-times brutal prioritization to make the most of limited resources.
When I'm not doing knowledge work, I'm an avid hiker, cheese eater and maker, mushroom enthusiast, and amateur furniture-builder.
Zola Batty McKoda, Chief Snooperviser Officer
I'm a rescued husky mix with cerebellar disease and permanent puppy antics. At work, I meticulously snoopervise everything that happens at knowledge with sass. I give freedom to my team without micro-managing, and I'm the official maintainer of work-life balance. I believe that most problems can be better solved after a quick walk outside and a snack.
My strengths lie in my ability to keep calm under pressure, a laser-like focus on maintaining a consistent schedule, and the ability to sniff out where problems and opportunities lie.
When I'm not doing knowledge work, I'm an avid hiker, cheese eater, and squeaky-toy killer.
Knowledge management experience
My knowledge management experience is just as varied as my background. I have:
Migrated docs
I've migrated several knowledge bases/wikis to new platforms, including requirements gathering, tool evaluation, selection, and procurement.
Audited & reorganized docs
I've audited and completely redesigned information architecture for both internal and external knowledge bases.
Launched docs
I've implemented the first formal knowledge base/technical documentation for several teams.
Evolved docs
I've transitioned existing knowledge bases from how-to/transactional docs to a more balanced mix of how-to, conceptual, and tutorial documentation.
Trained on docs
I've trained coworkers and managers on new knowledge management tools, style guides, writing, and processes.
Revived docs
I've revived several stagnant knowledge bases, most for internal policies and procedures, getting much higher content contribution and usage.
Strategized docs
I've created holistic content strategies so that support and marketing materials complemented and cross-referenced each other.
Advised on docs
I've advised customers on roll-out, buy-in, information architecture, and knowledge management best practices.
Writing experience
I've worked on these types of documentation:
Customer docs
I've written customer-facing software support documentation, including how-to, conceptual overviews, tutorials, and orientation materials.
Internal docs
I've written internal policy and procedure documentation, including detailed how-tos and more general company policies.
Training docs
I've created training and onboarding materials, guides, and videos to match user personas of varying technical backgrounds and skills.
Software docs
I've created and developed changelogs, release notes, and product newsletters where none previously existed.
Software micro-copy
As a product manager, I've written and revised software copy, including app labels and text, micro-copy, and tooltips.
API docs
I've updated existing API documentation using the OpenAPI specification and Redoc.
Marketing docs
I've managed UX designer relationships to rebrand and overhaul marketing websites and written blog posts.
Finessed docs
I've helped standardize existing documentation for format, style, and structure, both as an employee and a freelance writer.
Why "with sass"?
The title comes from two places:
knowledge management (n):
the framework or process an organization uses to identify, store, organize, and share information
sass (n):
an appealingly exciting, lively, or spirited quality
I've used a #withsass hashtag for a lot of my adventures: #runnerwithsass, #triathletewithsass, #hikerwithsass. When I hiked the entire Appalachian Trail in 2018, my trail name became Sassafras. I hiked with a lot of sass, so much so that some hikers told me they needed "a little less sass, and a little more fras" from me.
This sassiness shows up in every area of my life. But it's especially relevant to knowledge management, which sometimes is viewed as a boring, dry, or "necessary" (but not fun) area.
Good knowledge management can make your life easier, your coworkers' lives easier, your customers' lives easier.
It's the ultimate act of giving great service to yourself and others, and--when done right--can free up everyone's time and resources to be spent on more meaningful or useful pursuits.
knowledge with sass can make it far easier to live with sass. And that's a goal I want to help everyone achieve.