A mobile-first development paradigm focuses on developing functionality for mobile devices first and desktop devices thereafter. A mobile-first strategy is based on the premise that once the mobile design questions are answered, designing for other devices will be easier. — UXPin
Conversely, a desktop-first paradigm starts with development for desktop and laptop devices and then strips away features to fit on smaller form factors and to account for the lack of “on-hover” functionality.
Given that the vast majority of my company’s users use desktop devices to access their accounts, I was hesitant to adopt a mobile-first approach. In essence, our…
I thought that I’d share a naming convention that I have started using for Salesforce report types. As shown in the snapshot, the naming convention uses “IX” for left outer joins and “IXI” for inner joins. I also started using a pseudo SQL syntax in the Description field. In the snapshot, Users and Contacts are standard Salesforce objects, and Participants is a custom object.
Anyway. That’s it. Short and sweet. I hope you find it useful.
For me and my Technology department, the Salesforce acquisition of Slack can’t come soon enough. With the Slack acquisition comes the hope that Salesforce will replace Chatter with Slack. While Chatter is functional, its annoying bugs and feature limitations are maddening. Here’s a list of everything that I’m hoping a Salesforce-Slack integration will fix.
Paste 2x — The first attempt to paste into a Chatter Post fails, but at least the second time works. ;-)
Jumping Screen — Upon putting focus on the Post box, the case detail page shifts down. …
The “Silicon Valley” TV show was a brilliant HBO satire about companies and culture in The Valley. The third season of the show portrays a Steve Ballmer-like CEO who incessantly touts his oversimplified business diagram, which he calls “The Conjoined Triangles of Success”.
Low-code/no-code platforms are all the rage. In this post, I’ll provide an overview of the low-code movement including — what low-code is, what the benefits are, and what options are out there. I’ll also dive into why my company chose Salesforce as its low-code solution, and I’ll provide our lessons learned and limitations found.
Before we dive into what low-code is, let’s briefly talk about what traditional code is. As we all know, code looks something like this:
As you can tell by my blog posts, I am a huge fan of Google Workspace. In fact, back in 2016, I blogged about the advantages of Google Workspace vs. Microsoft 365. When I joined LT Trust, we were a small company with little appetite for a major culture shift to Google Workspace. When the pandemic rolled around, we had to step up our collaboration game, but we had to do so quickly and smoothly. The early days of the pandemic were definitely not a good time to disrupt the company with a transition to Google Workspace. …
Salesforce is a fantastic platform to bring together all types of users — technology, business, partners, and customers. Since many businesses already use Salesforce, it provides a low-code solution without adding yet another platform to the enterprise. Sales and other business units love Salesforce, so engagement and adoption couldn’t be better. Also, Einstein Analytics provides the eye candy that users are gaga over.
However, Salesforce is not without its challenges and frustrations. For me, the biggest frustration has been with Identity Verification and Multi-factor Authentication (MFA) in Customer Communities. …
Building team culture and camaraderie is difficult with virtual meetings. In lieu of face-to-face collaboration, we should look for ways to mitigate barriers to communication and innovation. Although it’s hard to put a dollar figure on it, there is something to be said for a fun and engaging work environment, even if it is virtual.
The rules of the game are simple:
I’m a big G Suite fan, but lately, I have been frustrated with Google Meet/Hangouts. I understand that I should expect some limitations due to the fact that Google Meet is 100% browser-based, but it’s frustrating nonetheless. Meet’s user interface lacks intuitive usability. In addition, you cannot synchronously call a co-worker via Google Chat. My latest frustration is that Meet doesn’t support virtual backgrounds; however, I found the following workarounds.
These workarounds will depend on your operating system and whether you are using a green screen.
Snap Camera — Has a lot of fun foregrounds…
This post is a continuation of a multipart blog series about Technology Leadership Spectrums. The values of technology leaders fall on a spectrum much like the beliefs of politicians fall on the left or the right of the political spectrum. In this installment, I’ll evaluate the opinions related to the means of team communication, the importance of efficient communication, and the value of on-site employees.