Poor Design
NOTE: This is the only purely technical challenge.
CAUSES
Poor design is usually caused by vague or incomplete requirements (garbage in, garbage out). But sometimes the problem is simply hubris.
REMEDIES
Effective design requires talented technical leadership. Business leaders can support their technical colleagues by asking the right questions and promoting a flexible and modular solution that will address immediate and future needs.
Sometimes the simplest architecture is the best. Avoid custom solutions where ever possible. Ask tough questions of technical vendors that attempt to sell specialized features.
Technical architecture should accommodate future changes – business needs will change, so the technology solution must be easily added to or modified for years to come.
During her time at Glenbrook, Erin focused on client engagements in business payments, cross-border transactions, bill payment, and the intersection of corporate finance, banking, and ERP/accounting. She has nearly twenty years of experience leading increasingly complex payment initiatives for corporate clients and advising financial institutions and payment technologists on the development of their payment capabilities.
Erin is also the founder of Forte Financial, a consulting firm focused on corporate finance efficiency, technology, and process improvement. She is a past president of the Financial Women’s Association of San Francisco and also a two-term past president of the San Francisco Treasury Management Association. Erin is no longer with Glenbrook, but contributed greatly during her time at the firm.