What’s the actual problem?
Summary
Users complained about a Salesforce page on tablets, leading to a review that revealed multiple similar flows with Aura components. While consolidating flows and switching to Lightning Web Components seemed like a clear plan, the real issues were simpler—font color and static text that needed dynamism. The key lesson is to dig deeper into user pain points before applying technical fixes to ensure changes address actual business problems effectively.
Takeaways
- Clarify true user pain points before proposing technical solutions.
- Consolidate similar flows using decision elements when appropriate.
- Favor Lightning Web Components over Aura components for better performance.
- Address user interface details like font color and dynamic text carefully.
- Validate that solutions resolve business issues, not just technical ones.
In a recent client meeting, they shared that their users complain about a particular page when using Salesforce on a tablet. Upon reviewing the page, I noticed the page displays one of several flows, based on a status, and includes several Aura components. The flows were very similar and Lightning Web Components (LWC) are better than Aura components. So technically, it would be easy to recommend merging the flows into one with decision elements, and replacing Aura with LWC. In today’s meeting, I explained these points and told them I would make the necessary changes. However I also asked them for more information about their pain points, to ensure the proposed changes would make a difference. As it turns out, the users complained about a font color and some static text needed to be dynamic. The takeaway This is a reminder that even though it’s easy to jump in and fix their technical issues, it may not resolve their business issues.