Posts

Recently I posted 5 simple changes you can make to transform organisations. Let’s unpack the 1st, “Outcomes not Outputs” An outcome is defined as “direct, tangible results of activities or processes” and I’ve personally experienced lots of teams are great at measuring them. Velocity; number of user stories delivered; or heaven forbid, the number of lines of code written (please don’t do this). But story points mean nothing (one team’s 100 could be another teams 20) and that means also that velocity is also meaningless especially when comparing between teams....

Projects would be quicker, cheaper & delivered more efficiently if stakeholders were willing to effectively prioritise. Mental load of employees would be drastically reduced. It’s a win-win-win-win. This LinkedIn Post did a great job about explaining the reasons why. Practical Tip: Introduce a WIP Limit to reduce context switching. Manage the flow of work. #QuickTip

Well maybe not exactly the same… But as the famous saying goes… “History doesn’t repeat itself, but it often rhymes.” Having re-read and reflected on this article (On LinkedIn / On my blog) I wrote in 2022 it became clear that the fundamentals of how to deliver value with Salesforce (and projects in general) are still the same. (Well) define the business problem you are trying to solve and/or the business value you are trying to achieve....

YouTube is now actively hostile to users without a premium subscription or an Ad blocker. Yesterday I put on a YouTube video to listen to under the shower. In the 10 minutes it took, there were 6 advert segments, each containing 2 ads, some couldn’t be skipped, some of which wouldn’t have ended unless I did skip and 1 creator advert within the video itself. The actual content was less than 3 minutes....

The following article is an article intended to describe some of the key things to consider when designing Salesforce architecture. It contains real anecdotes from my decade long career working with enterprise clients implementing Salesforce and combines this experience with the best of the Salesforce Well-Architected framework although I hope the principles described are equally applicable when implementing other software. TLDR: Great Salesforce architecture is intentional, simple & flexible. Ensure you are working on the right thing, making sure your architecture is simple and easy to understand and flexible enough to handle the inevitable missed / new requirements....