CRM
Design, implementation, adoption
"It's faster to ask the previous rep, so nobody reads the records." I hear this on almost every CRM project.
A summary does not tell you what to do next, so the next rep asks the last one.
Records nobody reads only cost input time. A CRM gets used when it is a place to decide, not a place to read.
Above all, I genuinely love CRM. That is why I build one too. The pattern that survived 40+ redesigns is Revenue CRM.
Why CRM implementation fails without Revenue Architecture