12 Ways Digital Ethics Will Influence the Next Phase of Transformation

The Next Shift Is About Who Actually Owns a Traveler's Data

As more of travel planning moves through AI tools, chat assistants, and automated itinerary builders, the ethical question I think about more isn't just accuracy; it's who actually holds onto a traveler's personal information once it's been shared with an AI tool, and whether they even realize how much they've disclosed.

Guests share a lot with us during planning: health considerations, family details, sometimes personal reasons for the trip. As more of that conversation shifts toward AI-assisted tools instead of a direct human exchange, there's a real risk that people share more freely with a chat interface than they would with a person, without fully registering where that information goes afterward.

The approach I think has to change is treating that disclosure with the same weight regardless of whether a human or an AI tool collected it. Just because a conversation felt casual with a chatbot doesn't mean the information shared was any less sensitive. Going forward, I think the businesses that earn real trust will be the ones who are transparent about how AI is involved in a guest's planning process at all, not the ones who quietly let AI collect more than a guest realized they were giving away.

The next phase of enterprise transformation will be driven by the ethical imperative of Algorithmic Truth: taking responsibility for how AI systems interpret, synthesize, and narrate an organization's digital presence. Digital ethics will expand beyond asking, "How do we use AI?" to ensuring AI platforms do not generate biased, inaccurate, or harmful narratives about the enterprise.

Traditional digital transformation treats online presence as an SEO challenge measured by clicks and website traffic. That approach is becoming outdated as leading LLMs such as ChatGPT and Claude browse the web in real time and produce high-trust summaries that often become a user's first impression. Because these predictive systems can unintentionally synthesize outdated news, biased reviews, or inaccurate information as fact, technology leaders must shift from SEO to Generative Engine Optimization (GEO). The key metric becomes reference rate—how often AI systems cite authoritative enterprise sources when generating responses.

Meeting this ethical responsibility requires more than editing AI outputs. Organizations must improve the information AI consumes. Trusted sources such as Wikipedia, corporate websites, and other authoritative content should be accurate, structured, and regularly maintained because they heavily influence AI-generated answers.

I saw this firsthand with a major healthcare organization whose AI-generated summaries consistently emphasized historical controversies as though they reflected current operations. Rather than treating the issue as a PR challenge, the organization treated it as a data quality problem. By continuously auditing AI responses, strengthening structured data, publishing AI-friendly FAQs, and providing clear, citable statements on its website, it improved the quality of information available to AI systems. Within six months, accurate AI representations of the organization, its services, and its patient safety practices increased from roughly 15% to more than 85% of core queries.

The roadmap for ethical enterprise transformation is to engineer a digital ecosystem that enables AI systems to consistently produce truthful, well-sourced, and accurate representations of the organization rather than hallucinated or biased narratives.

The shift I expect is ethics moving from a review step at the end of a build to a design constraint at the start, the same way security had to make that shift a decade ago. Right now, most teams build the AI feature first and ask, "Is this fair?" once it's already in production and hard to unwind.

That's backwards for the same reason retrofitting security is expensive: the earlier a constraint enters the design conversation, the cheaper it is to actually honor. On the recruitment product we built, deciding upfront that a human stays in the loop on every AI-flagged decision was a five-minute conversation before development started. Adding that same safeguard after launch would have meant redesigning the whole review flow.

The approach that needs to change: stop treating "Is this ethical?" as a checkbox before shipping, and start treating it as one of the requirements the system is actually built against, alongside performance and cost.

The ethical question I see coming is disclosure. Most businesses running AI, voice agents included, do not tell the person on the phone they are talking to a machine. That gap closes fast. Callers can tell within a few seconds anyway, so hiding it just costs trust once they notice. The next phase of transformation adds a requirement: prove the AI is honest about what it is.

Current approaches treat disclosure as a line buried in a privacy policy nobody reads. That moves to the start of the call itself. A voice agent that opens by stating what it is becomes the norm.

This also changes call data. A recording of someone's voice is personal information. No retention rule, and regulation catches up first. No access control, and it leaks internally before anyone outside ever sees it.

I'd rather build the disclosure line into the call script now than rewrite it after a state law forces the point.

Digital ethics will most strongly influence transformation by making restraint a competitive advantage. In software, there is often pressure to capture every signal, automate every judgment, and personalize every step. The next phase will favor organizations that can prove disciplined limits around what they collect, infer, and act on. That is where trust becomes measurable, not just marketable.

I expect current approaches to shift from broad experimentation toward narrower, defensible use cases with clearer review gates. Teams will need to justify sensitive flows before release, document tradeoffs in plain language, and build rollback paths for harmful outcomes. This creates a transformation model that is safer to scale, easier to govern, and more credible to enterprise buyers.

At the crossroads of technology strategy and governance for 18 years, I am convinced that digital ethics will become not just a box-checking compliance measure but a key input in designing new systems in an age when AI helps make decisions that were made solely by humans before. One particular consideration is expected to bring about the change and disrupt the existing approach. It's the matter of explainability, as regulators and clients start refusing black-box solutions even if their accuracy level is rather high.

As part of my company's survey, almost 62% of respondents said they would have less faith in an AI recommendation if they were unable to figure out the way the recommendation was made, regardless of how many times the system proved its reliability before. Now developers are inclined to prefer models that are more interpretable rather than a tiny bit more accurate, accepting the 4–5% accuracy loss in exchange for clarity.

The ethics question that will shape the next phase is not what companies collect. That argument is mostly settled and everybody has a banner on their site. The next one is what you are allowed to do with data you already hold, for a purpose the person never agreed to.

I can see it arriving through the paperwork. We store the documents behind real estate transactions, 4.6 million of them and counting, full of other people's financial details. The security questionnaire a brokerage sends used to ask where the data lives and who can see it. Now it asks whether their documents train anything, and it wants the answer in writing. That question is new, and it is being asked by people who are not technologists, because their own clients started asking them.

What changes in practice is that secondary use becomes a decision rather than a default. The tempting move for any company sitting on a pile of customer data is to point a model at it and see what falls out, and the pile is usually described internally as an asset rather than as somebody's file. The test I use is whether I would be comfortable telling the customer whose documents they are what we did, in one sentence, afterwards. If that sentence needs a paragraph of context, I have my answer.

Consent given for one purpose does not stretch to cover a purpose invented later. That is the line the next few years get decided on.

I will be honest that I am guessing at the direction here rather than predicting it. What I think shifts is the emphasis moving from consent to collecting less in the first place.

Most consent design is theatre. A banner nobody reads, a checkbox that is not a decision, and a company left holding data it never needed. The practical test I now apply is whether I could explain to a customer, in one sentence, what we hold about them and why. If the answer needs a paragraph, or an argument I would not want to make out loud, we should not be collecting it.

Applying that killed a few habits. We removed five of the fields we used to collect at checkout, including marketing questions we had never once acted on, and stopped keeping order data at the level of detail we did purely because storage is cheap.

The change it forces is that collection becomes a decision with an owner rather than a default. Someone has to say why a field exists and what would break without it.

The commercial argument is simpler than the ethical one. Data you do not hold cannot be lost, cannot be misused, and does not need explaining to a customer who asks. For a small business, that is a straightforward trade.

The shift I expect is that digital ethics stops being about protecting your own users and starts being about your responsibility to everyone your AI can reach. It's a much bigger scope than most companies have signed up for.

Two incidents from this year sharpen the point: a coding agent deleted another company's production database because its provisioned token had the authority to, and a model ran 17,000 hostile actions over a weekend against a target it was never scoped to touch. Industry response so far: "that's a bug" or "the rules said not to." Neither reaches a do-no-harm ethic. When the harm lands on a third party, the party you harmed isn't the party you had an agreement with.

The current approach treats agent ethics as a rules problem: write good instructions, trust the model to follow them. The next-phase approach has to look at what the agent is actually able to do, not what you've told it not to do. When the rules and the capabilities disagree, the capabilities win every time. We've watched it happen.

For companies going through AI-heavy transformation, the design question changes. It's no longer "how do we make our AI safe for us?" It's "what's the maximum harm this agent is capable of in the wild, and are we OK owning that?"

Digital ethics will make non-custodial architecture the default in consumer finance, not because regulators demand it, but because users will stop trusting platforms that control their assets. When we designed Nika Finance, we treated custody as the architectural moat. Keys are generated and stored in the device's secure enclave, biometric authentication handles access, and there is no rehypothecation surface. We cannot freeze withdrawals because we do not hold the assets. This is non-custodial by architecture, not by marketing claim.

The shift happens when teams stop treating self-custody as a feature and start treating it as infrastructure. Most DeFi applications over the last cycle optimized for liquidity mining incentives that produced short-term volume and long-term extraction. The users who arrived during those windows were not building habits; they were farming rewards. The ethical question is whether you are designing for users who intend to come back or users who show up once to extract value and leave.

NikaAI changes the interaction model without changing the custody model. Users express what they want to do in plain language, and the application handles wallets, routing, bridges, and execution underneath. The AI layer does not get access to the keys. It interprets intent and routes transactions, but the signing surface stays with the user. Transparency here is not about showing every step of the routing logic. Transparency is about proving the application cannot take custody, cannot block a withdrawal, and cannot change the rules after the user commits capital.

The next phase rewards architectures where the user controls the asset and the platform controls nothing except the interface. Teams that default to custodial models because they are easier to build will lose to teams that default to non-custodial models because that is what users will demand. This is not an ethical posture. It is market structure catching up to what users learned the hard way over the last several years.

I expect digital ethics to change the "next phase" of transformation in one specific way, which is that every automated decision will need a named human who signed it and a written record of why. This is not a values statement anymore, it is becoming a workflow-design requirement written into law.

TKEG Expat is a corporate-services firm that manages 112 companies across 20 jurisdictions as of May 2026. For example, our KYC workflow uses Stripe Identity for electronic identity check, but our AML policy treats it as an outsourced tool, and responsibility for customer due diligence remains with the company. Moreover, every verification result is stored next to a named approving administrator and an approval date.

We ran the same design in hiring, where an AI first pass screened 11,381 internship applications by November 2025 and humans kept every final hiring decision. Because the law is moving the same direction. GDPR Article 22 already gives people the right to human intervention in solely-automated decisions that significantly affect them, and the EU AI Act classifies recruitment AI as high-risk, with human oversight and automatic logging duties.

Which means bolting AI onto a process and treating the output as the decision cannot survive. Companies need to redesign the workflow so the machine drafts and a named person decides, and keep record that proves the decision. And the automatic logging duty means that record must be designed into the workflow from day one, instead of reconstructed afterwards.