This document provides a framework for planning a transition to a low-code platform (LCP) and tool (LCT). It prompts the reader to consider their reasons for pursuing low-code, the scope of their initial problem and tool, key stakeholders, and how to manage the change. Examples are given under each prompt to spark ideas. The overall structure is meant to help crystallize intention and plan the first step of a journey to low-code development.

1. Credit: Vaibhav Vaidya, 2023
https://www.linkedin.com/in/vaibhav-a-vaidya/
Crystallizing Intention
Your journey to Low-code: Step 1
Abbreviations:
LCP = Low Code Platform
LCT = Low Code Tool developed on an LCP

2. Why low-code? Why now?
A checklist of YOUR reasons
• — Your reasons here —
Some ideas:
• O
ffl
oad SecOps and CI/CD to LCP
• Evolve business features fast in LCT
• Grow what any one developer can deliver
• Deliver more projects as a consultant
• Reduce infrastructure maintenance overhead
• Reduce dependence on outsourced consultants
• I want my neighbor to envy me
• World peace is a well coded tool

3. What is your problem’s scope?
Users / Scale / Functionality / Integrations
• — Your thoughts here —
Some ideas:
• A tool to make a part of my own job easier
• A tool for a single team
• Customer facing tool for unto 400,000 customers
• Ticketing and CRM platform connecting to
product onboarding via API
• Include future scope: e.g. LCTs for adjacent
business teams needing a consistent UI
experience

4. Who are the stakeholders?
• — Your thoughts here —
Some ideas:
• I have to convince my boss
• I need to poll the users for approval
• I’ll have to enlist developers to code it
• Our data analyst will need to
fi
gure out how to pull
data from this new tool
• I’ll need sign-o
ff
from our
fi
nance team that doesn’t
like changes to our cost structure on the business
value of the change

5. How might you manage the change?
• See this article on our own experience
• See execution notes