No-code product development

Anyone familiar with product development should recognise the image below. It’s a schematic for a start-up idea I was working on several years ago – for an employee engagement, reward and recognition app. It was the result of a number of workshops with a digital agency covering problem statements, user scenarios, workflow solutions, personas, UX/UI design and back-end architecture frameworks.

At the time, the cost quoted to build the MVP was easily 5-6 figures – and even to get to that point still required a load of work on story boards, wire frames and clickable prototypes….

Now, I would expect the developers to use something like a combination of open-source and low-cost software applications to manage the middle-ware functions, dial-up a basic cloud server to host the database and connect to external APIs, and commission a web designer to build a dedicated front-end. (I’m not a developer, programmer or coder, so apologies for any glaring errors in my assumptions…)

The growth in self-serve SaaS platforms, public APIs and low-cost hosting solutions (plus the plethora of design marketplaces) should mean that a developer can build an MVP for a tenth of the cost we were quoted.

Hence the interest in “low-code/no-code” product development, and the use of modular components or stack to build a range of repetitive, automated and small scale applications. (For a dev’s perspective check out Martin Slaney’s article, and for a list of useful resources see Ellen Merryweather’s post from earlier this year.)

There are obvious limitations to this approach: anything too complex, too custom, or which needs to scale quickly may break the model. Equally, stringing together a set of black boxes/off-the-shelf solutions might not work, if there are unforeseen incompatibilities or programming conflicts – especially if one component is upgraded, and there are unknown inter-dependencies that impact the other links in the chain. Which means the product development process will need to ensure a layer of code audits and test environments before deploying into production.

I was reflecting on the benefits and challenges of hermetically sealed operating systems and software programs over the weekend. In trying to downgrade my operating system (so that I could run some legacy third-party applications that no longer work thanks to some recent systems and software “upgrades”), I encountered various challenges, and it took several attempts and a couple of workarounds. The biggest problem was the lack of anything to guide me in advance – that by making certain changes to the system settings, or configuring the software a certain way, either this app or that function wouldn’t work. Also, because each component (the operating system, the software program and the third party applications) wants to defend its own turf within my device, they don’t always play nicely together in a way that the end user wants to deploy them in a single environment.

App interoperability is something that continues to frustrate when it comes to so-called systems or software upgrades. It feels like there needs to be a specialist area of product development that can better identify, mitigate and resolve potential tech debt, as well as navigate the product development maintenance schedule in anticipation of future upgrades and their likely impact, or understand the opportunities for retrofitting and keeping legacy apps current. I see too many app developers abandoning their projects because it’s just too hard to reconfigure for the latest system changes.

Next week: Telstar!

 

 

 

Antler Virtual Demo Day

As with other virtual demo days I have attended this year, it was remarkable to hear how far the teams in Antler’s Sydney Cohort #3 had progressed in light of the current pandemic and associated lock-down restrictions.

Each participating team was categorised into an industry sector:

Consumer Tech

Remote Social is designed to connect remote and hybrid teams. The ethos is that with the shift in working patterns (heightened by the current pandemic) corporate culture and organisational engagement are “at risk”. The solution aims to foster socialisation and build culture through curated games and activities. Claiming to have generated over 200 organic signups, including team members at big tech brands, the founders are adopting a “bottom, land and expand” customer acquisition strategy. In addition to a seat-based subscription model, the platform will also offer a revenue share for marketplace providers.

Coder One claims to be “the home for AI sports”. The team describe their project as an API platform for AI games, with unique combination of AI and e-sports. The goal is to make AI and programming more accessible via an AI Sports League, where bots compete, programmed by developers. With more than 250 registrations for an upcoming competition, the team are also looking to secure sponsorship deals. The commercial model has three components: free access to programs for developers, individual subscription fees to access games/tournaments, and corporate fees to access talent for potential recruitment.

Feather is an online platform which enables instructors and creators to deliver and monetise their digital services. According to the founders, existing tools are not fit for purpose, complex or clunky. Initially targeting yoga teachers, the solution will sell tiered subscriptions, plus take a small revenue share. The team also see themselves as part of the “creator economy”, but I was confused by the name – is it a deliberate attempt to suggest a link to Dumbo Feather magazine? Plus, there was some feedback that the platform may be vulnerable once tools like Zoom start putting up more pay walls.

Tactiq is a tool to “capture valuable insights from remote meetings”. The founders claim it can be used with any conferencing software, and is platform agnostic (although currently limited to a Google Meet via a Chrome Extension). The product, essentially “speech to text plus”, also generates AI assisted summaries, and the team has attracted over 100,000 users from around 4,500 organisations. Pricing is $9 per user per month, plus $20 per month to access team functionality. While the team appears to know and understand their target users, they were questioned about privacy and security issues. Although the transcription content is not stored on the platform, my experience of other similar tools is that once they are integrated, they have a tendency to “take over” and insert themselves, unprompted, into e-mail and calendar applications – “you seem to have a meeting now – would you like me to record it?”

SaaS

Upflowy wants to help B2B companies improve their customer conversion rates. Intended to be a “no-code” sign-up engine, the team explained that from their experience, in-house developers tend to focus on product features, rather than improving the sign-up experience. Typically, in-house sign-up optimisation is slow, expensive or totally non-existent – the key issues being scaleability and reliability. Essentially a form builder, the solution enables A/B testing, and claims to deliver a 40% improvement in conversion rates (compared to 17% improvement achieved with other optimization tools).

Flow of Work Co is positioning itself as the “Future of Work SaaS”. With a mission to help companies to retain the best people, it is HR tech using AI in the form of a smart matching engine to identify in-house talent, based on proprietary ontology. It also helps employees to find development resources, as well as to match projects with in-house talent. According to the founders, talented staff leave because they are bored or lack career development. With an initial focus on software companies, the team then plans to tackle the financial services sector. The team was asked about integration with existing HR tech stacks, and how they ensure objective assessment of competing project candidates – but it wasn’t so clear how they achieve either.

Portant is an end-to-end project reporting tool, designed to be a “consolidated single source of truth”. Asked why existing project management tools don’t work, the founders identified a number of factors: teams are using different tools, the process is often repetitive and/or highly manual, or project tracking typically relies on data from different sources. The team have launched an MVP on Google Workspace Marketplace, and will soon launch on Microsoft AppSource (and appears to use AWS Comprehend as the analytical tool?). There is an SaaS pricing model, and content privacy is ensured via end-to-end encryption plus the use of private keys.

StackGo helps clients achieve stronger B2B sales via SaaS marketplaces, rather than relying on direct sales. However, the initial setup costs and effort required to connect to existing SaaS marketplaces can be daunting. With an approach based on “build once, deploy many”, StackGo enables users to connect to multiple SaaS marketplaces via a single solution. However, the team, did not explain what the setup costs are for StackGo nor were they very specific about the price range or typical sales value their clients achieve – “free to hundreds of dollars per month”.

EdTech

GradVantage wants to reduce the cost of getting graduates job ready, and reckons it can save employers $30k per new hire. Offering a personalised learning experience for each user, the founders have adopted a “Slack” model – team first, then enterprise sale. Acknowledging that the EdTech sector is crowded, the team think their point of differentiation is the fact that they are a career-entry solution, and not in the K-12 market. The focus is on tech talent and SaaS vendors. Employers pay per learner, and the platform saves time and reduces on-boarding costs. Typically, 30% of program content is about tech applications, and 70% on how to use the tech. A more fundamental issue is the huge gap between university courses and actual job requirements.

HealthTech

eQALY is an integrated tech platform that enables the elderly to achieve a higher quality of life in their own home, by predicting their individual needs in advance, and identifying the right Home Care Package funding (which can be worth up to $26k). Using 360 degree data inputs, a risk model, and a proactive care plan, the product takes into account client needs as well as family concerns, plus financial considerations. Although the aged care industry is regarded as being slow to adopt new technology, the founders plan to focus on aged care organisations, who will then distribute predictive data and analytics to care providers and managers. The platform is tech agnostic but IoT devices, AI tools and virtual assistants can be integrated, plus new voice analysis technology is emerging that can monitor client well-being, and
all of the activity monitoring tech is passive. meaning the end user does not have to worry about learning new applications.

Retail and E-Commerce

The One Two is a very specific, and very targeted, D2C solution offering a hyperpersonalised service for fitting and buying bras. According to the founders, current customer experience suffers from ill-fitting products, poor product design, bad materials, and inadequate size configurations. As a result, customers feel overwhelmed and give up. The basic product IP has been tested, along with an on-line measuring and fitting tool, combining to provide better customer diagnosis and product tips. The team have already secured a startup partnership with a global lingerie manufacturer and distributor.

m8buy did not make much sense to me. Maybe I’m the wring demographic, but why would anyone want to “shop online with [their] friends”? Describing itself as “a social layer on any e-commerce store”, it feels like this is aimed at the “buy now, pay later” audience.
According to the founders, merchants will only pay a commission (“low single digit %”?) on successful sales. But it’s not clear whether this is a group buying service, a discount marketplace, or a loyalty programme, nor how it will be differentiated within the Shopify marketplace.

PropTech

Sync Technologies is a digital solution for construction industry – with the tag line of “turning data into insights”. The problem being addressed can be summarised as follows: 1) Building
sites are fragmented and complex 2) Progress reporting and bottleneck identification is poorly done 3) 12% of a typical job has to be reworked 4) 80% of projects are late and/or run over budget. Using a digital twin concept, the solution aims to provide a “single source of truth”, and the team are already working with some key firms, and have 2021 forecast revenue of $2m.
Key obstacles to overcome are entrenched on-site behaviours, and slow the tech adoption across so many stakeholders in the construction industry. The founders claim to have identified the solution via their Construction Assistance System which offers better project and status visualisation via the digital twin.

Next week: Version / Aversion

The Ongoing Productivity Debate

In my previous blog, I mentioned that productivity in Australia remains sluggish. There are various ideas as to why, and what we could do to improve performance. There are suggestions that traditional productivity analysis may track the wrong thing(s) – for example, output should not simply be measured against input hours, especially in light of technology advances such as cloud computing, AI, machine learning and AR/VR. There are even suggestions that rather than working a 5-day week (or longer), a four-day working week may actually result in better productivity outcomes – a situation we may be forced to embrace with increased automation.

Image Source: Wikimedia Commons

It’s been a number of years since I worked for a large organisation, but I get the sense that employees are still largely monitored by the number of hours they are “present” – i.e., on site, in the office, or logged in to the network. But I think we worked out some time ago that merely “turning up” is not a reliable measure of individual contribution, output or efficiency.

No doubt, the rhythm of the working day has changed – the “clock on/clock off” pattern is not what it was even when I first joined the workforce, where we still had strict core minimum hours (albeit with flexi-time and overtime).  So although many employees may feel like they are working longer hours (especially in the “always on” environment of e-mail, smart phones and remote working), I’m not sure how many of them would say they are working at optimum capacity or maximum efficiency.

For example, the amount of time employees spend on social media (the new smoko?) should not be ignored as a contributory factor in the lack of productivity gains. Yes, I know there are arguments for saying that giving employees access to Facebook et al can be beneficial in terms of research, training and development, networking, connecting with prospective customers and suppliers, and informally advocating for the companies they work for; plus, personal time spent on social media and the internet (e.g., booking a holiday) while at work may mean taking less actual time out of the office.

But let’s try to put this into perspective. With the amount of workplace technology employees have access to (plus the lowering costs of that technology), why are we still not experiencing corresponding productivity gains?

The first problem is poor deployment of that technology. How many times have you spoken to a call centre, only to be told “the system is slow today”, or worse, “the system won’t let me do that”? The second problem is poor training on the technology – if employees don’t have enough of a core understanding of the software and applications they are expected to use (I don’t even mean we all need to be coders or programmers – although they are core skills everyone will need to have in future), how will they be able to make best use of that technology? The third problem is poor alignment of technology – whether caused by legacy systems, so-called tech debt, or simply systems that do not talk to one another. I recently spent over 2 hours at my local bank trying to open a new term deposit – even though I have been a customer of the bank for more than 15 years, and have multiple products and accounts with this bank, I was told this particular product still runs on a standalone DOS platform, and the back-end is not integrated into the other customer information and account management platforms.

Finally, don’t get me started about the NBN, possibly one of the main hurdles to increased productivity for SMEs, freelancers and remote workers. In my inner-city area of Melbourne, I’ve now been told that I won’t be able to access NBN for at least another 15-18 months – much, much, much later than the original announcements. Meanwhile, since NBN launched, my neighbourhood has experienced higher density dwellings, more people working from home, more streaming and on-demand services, and more tech companies moving into the area. So legacy ADSL is being choked, and there is no improvement to existing infrastructure pending the NBN. It feels like I am in a Catch 22, and that the NBN has been over-sold, based on the feedback I read on social media and elsewhere. I’ve just come back from 2 weeks’ holiday in the South Island of New Zealand, and despite staying in some fairly remote areas, I generally enjoyed much faster internet than I get at home in Melbourne.

Next week: Startup Vic’s Impact Pitch Night

 

 

 

 

 

The new productivity tools

With every new app I download, install or have to use, I keep asking myself: “Do I feel more productive than I did before I downloaded it?” Comparing notes with a business associate the other week, I realised that the arsenal of daily tools I use continues to expand since I last blogged about this topic. At times, I feel like Charlie Chaplin in “Modern Times” trying to keep on top of this digital production line.

Image sourced from Wikimedia Commons

In particular, the number of communication tools (instant messaging and conferencing) keeps growing; document and file management continues to be a battle largely between operating systems; and most collaboration tools struggle to make the UI as seamless as it should be – so that the UX is all about the “process” for creating, updating and maintaining projects, and not the quality of outcomes.

So, as an update to my previous blog, here’s a few thoughts on recent experiences:

Meetings/Chat

Added to my regular list are Telegram, WeChat, UberConference, BlueJean and RingCentral. Meanwhile, Microsoft (Skype), Google (Hangouts) and Apple (FaceTime) all compete for our communications. (Even Amazon has its own conferencing app, Chime.) One of the biggest challenges I find is browser compatibility (when using via a desktop or laptop) – presumably because vendors want to tie you into their proprietary software eco-systems.

Project Management/Collaboration

Still looking for the perfect solution…. Products are either so hard-coded that they are inflexible, or so customisable that they can lack structure. I suspect that part of the problem is projects are still seen as linear (which makes sense from a progress and completion perspective), but we collaborate at multiple levels and tasks (with corresponding inter-dependencies), which don’t fit into a neat project timeline.

Document/File Management

I seem to spend most of my day in Google Drive (largely thanks to Gmail and Drive) and Dropbox (which continues to improve). I find Dropbox more robust than Google Drive for file management and document sharing, and it continues to expand the types of files it supports and other functionality. Whereas, with Drive, version control is a bit clunky, unless the document was first created in Google Docs.

Productivity

Overall, Google Docs is still not as good as MS Office (but does anyone use OneDrive, let alone iCloud/iWorks, for document sharing or collaboration?)

One thing I have noticed is that my use of native iOS productivity tools has dropped off completely – if anything, I am now using more MS Office iOS apps (e.g., Lens, OneNote), and some Google Docs apps for iOS. Plus the DropboxPaper iOS app.

CRM

I’m starting to use Zoho (having outgrown Streak) – and I’ve heard that there is even a Zoho plug-in that connects with LinkedIn, which I shall soon be exploring. But as with Collaboration tools, getting the right balance between rigidity and flexibility is not easy.

Next week: The first of three musical interludes….