I am fascinated by transactional nature of counter knowledge and public discourse which simulate (but don’t engender) counter-public spheres
I am responsive to the expressed and unexpressed wishes and needs of X.
I am empowered to create exceptional, remarkable, and secure experiences.
I understand my role in achieving X’s roadmap, embracing FinTech and wider community engagement, and enabling cost-effective hyper growth scale.
I continuously seek opportunities to innovate and improve X’s security posture.
I own and immediately resolve problems.
I create a work environment of teamwork and lateral service so that the needs of our customers and each other are met.
I have the opportunity to continuously learn and grow.
I am involved in the planning of the work that affects me.
I protect the privacy and security of our customers, my peers, and X’s confidential information and assets.
I am responsible for uncompromising levels of ethics, morals, and creating a safe, diverse, inclusive, and risk-taking environment.
I operationalize the basics so they flow like water out of the tap.
I strongly believe the best process is no process.
Anything that requires an explanation inhibits communication. Avoid nonsense words and acronyms. No rational reason to memorize a dictionary just to communicate effectively at X.
Communicate along the shortest path possible to accomplish the challenge at hand.
Make requirements less unintelligent. All designs are wrong, it is a matter of how much. No matter whom one is, everyone is wrong some of the time. Human nature. As a result, adjust accordingly.
Remove roadblocks and barriers. This comes in the form of deleting processes, policies, and many other hinderances. Delete parts of a process, policy, and many other hinderances. Then add back in what is really needed. Operationalize the basics so they flow like water out of the tap.
Simplification before optimization. Far too many times in R&D institutions does one optimize the widget that was never needed in the beginning.
Leapfrog, don’t imitate.
Question the question first, question your answer second.
Identify the Right Work and get it done.
Everyone is the SME. Everyone involved should have a basic understanding of the entire system, its constraints, and interfaces.
Start off on the foundation / principles. Then build or break from there. Design shouldn’t take too long. If design takes too long, the design is incorrect.
Automate.
Excessive meetings are a blight. Unless they provide value to every attendee, keep them short and / or find other approaches to accomplish the task at hand.
Frequent meetings are only needed when urgency exists, otherwise change to infrequent.
If there is nothing to add value to, drop off. It is rude to make individuals stay, wasting their time and attention.
Cross-boundary collaboration achieve greater results, be it higher margins, quick to market, and higher innovation / business transformation - increasing pace / execution. Communicate directly instead of hierarchy. Free flow of information between all levels. It is ok to talk directly and just make the right thing happen.
Pick common sense. If following a process or policy is risible, that process / policy needs to change.
Ensure constraints are associated to the individual who affirmed / created it. Such that one knows exactly whom to go to for why it exists.
The best process is no process. Costs nothing and can’t go wrong. Hence automation.
Leap frogging.
Get the Right Work Done
Question the question first, question your answer second.
Accelerate after figuring out the above items. Not rational to dig ones' grave faster.
If X takes too long, X is incorrect.
After repeating X, automate X.