✺  What we do

How to manage custom software design for B2E: A Successful Product VP’s Cheat Sheet. Part 2

Insight: How to manage custom software design for B2E. Cheat Sheet. Part 2
✺  Written by
Slava Tarasov
Managing Director
— bn digital strategy

Managing custom software design for the B2E (Business-to-Employee) segment requires a strategic approach that balances vision with execution, leverages existing strengths, and incorporates best practices. This is the second part of a cheat sheet that lists obvious-after-you-fail insights to navigate the complexities of delivering effective and efficient software solutions that meet the high expectations of corporate users.

✺  TOC

Get a Tenured Data Analyst Onboard

Securing business support in the form of SMEs is a given. However, what’s less obvious but equally crucial is bringing in someone who understands data structures. Every department typically has an individual responsible for generating the main reports for their unit. This person is the most knowledgeable in the organization about the data available in the company’s databases, whom to contact for specific details, and the cadence and timing of data updates. The value of a person who knows where and how to source your data is unparalleled.

Expect Performance Issues When Working with Large Datasets

Financial databases store vast amounts of data, particularly transaction data sets. Most of your reports will likely rely on these large data points, which can lead to performance issues. Slow report loading times decrease user interest in the report's value and increase frustration among project sponsors.To mitigate these issues, plan for performance challenges from the beginning. Aim for the fastest data rendering possible and insist on a scalable architecture that supports progressive data rendering. Setting up the architecture correctly from the start is crucial, as you may not have the opportunity to make significant changes later.

Athens

Design the process — get decision makers in the room

Gathering the necessary information to deliver a product involves various activities and methods. However, designing a working tool requires a different approach. It is crucial to obtain business approvals for the instructions provided to professionals within the business process created through the software product.Use strategic sessions wisely, as opportunities to get everyone on board with a new or updated process are limited. If you don’t get all the decision makers in one room or secure their approvals early on, you will likely face significant challenges down the line. Ensure that key stakeholders are present and engaged to streamline the decision-making process and facilitate smoother implementation.

Deliver Best Practices — Users Expect Smart Apps

Whenever possible, implement standard design practices such as following user behavior rather than imposing restrictions and incorporating extensive autosave features. Corporate users expect applications to perform with the same speed and ease as the most popular B2C apps. They won’t be concerned about your lack of resources or time to match the UX of mature billion-dollar products. Start by identifying the right type of interface and finding similar products. Market leaders have outlasted the competition and set the standards (and expectations) for your user base. By adopting their best practices and adhering to established patterns, you will align with users’ habits and save considerable time.

Want to stay informed? Subscribe to
our Newsletter and Personalize Your Experience 

Secure At Least One Designer for Your Team

With the rise of design thinking courses, the popularity of UX checklists, and numerous available frameworks, many people feel capable of taking on the role of a software designer. This often leads to delegating design responsibilities to front-end developers or BSAs to save resources. However, while this approach might save on designer costs, it can result in developers having to redo poorly planned products and missed opportunities. Engineers tend to focus on frameworks they are comfortable with or that are trendy, rather than pushing the boundaries to meet user needs. They might try to assemble something close to the request, but this rarely succeeds in practice. Engineers are typically preoccupied with controls and data streams, causing user goals to slip from their attention. A good rule of thumb is to have at least one designer for every five to ten developers.

Uncomfortable fork