Flagship service · IT Consulting · since 2017

Most companies have IT. Few have an IT design.

IT Design is LV3's hands-on consulting practice: we draw the chart your business will follow, and we sail the route alongside you. Business goals → data strategy → technology strategy → realisation → reflection — six steps, run as one structured engagement, grounded in DMBOK and PMBOK. We lead with design — and can take on the build too, from contract development to a proof of concept, when you need it. Confront emergencies with the power and expertise of IT Design.

ASIS
Migrate
TOBE
DIGITAL WORLD · NAUTICAL CHART

From the destination back. Then forward, step by step.

An IT Design engagement is a single voyage with six phases. We start from the business objective — not the technology — and only commit to the build once the destination, the route, and the constraints are explicit.

STEP 1

Business objectives

事業目標
STEP 2

Business management

事業マネジメント
STEP 3

Data strategy

データ戦略
STEP 4

Technology strategy

技術戦略
STEP 5

Realisation

実現
STEP 6

Reflection & improvement

改善
The six steps at a glance.
STEP 1
Business
objectives
STEP 2
Business
management
STEP 3
Data
strategy
STEP 4
Technology
strategy
STEP 5
Realisation
STEP 6
Reflection &
improvement

Two models. One coherent picture of the business.

Every IT Design engagement produces two layered artefacts. The Business model is the operational story (ASIS today, TOBE at the destination, the gap, the executive design). The Data model is the underlying resource map — what data exists, what's shared, what's unique, how it powers the business.

① BUSINESS MANAGEMENT · 事業マネジメント

For business goals— draw up a phased design, including a transition period, to gradually move the business toward its objective.

Organize ASIS and TOBE. Draw the route between them.

Organise where the business stands today (ASIS) and where the project should take it (TOBE). Map the gap, design the executive organisation that will close it, schedule the work in phases. The deliverable is a roadmap a CFO and CTO can both read.

  • 1Internal environment analysis
  • 2External environment analysis
  • 3Target setting
  • 4GAP arrangement
  • 5Executive organization design
  • 6Scheduling
② DATA STRATEGY · データ戦略

For data strategy— maximise data as a shared resource by visualising the shared parts of every department and every job.

Visualise the shared parts of the business. Treat data as a resource.

Investigate the common and unique parts of operations, then visualise the business with focus on the common parts. Identify the constituent elements of business activity, design data structures that support them, decide how data becomes a strategic resource — not a by-product.

  • 1Visualisation of operations and systems
  • 2Overall picture · common parts
  • 3Generalised elements · common parts
  • 4Generalised elements · unique parts
  • 5Resource utilisation plan
  • 6Data design supporting both
The 6×6 elements behind each model.
Business Management

Organise ASIS and TOBE (based on the purpose of the project) and draw a step-by-step roadmap for realisation.

  1. 1Internal environment analysis
  2. 2External environment analysis
  3. 3Target setting
  4. 4GAP arrangement
  5. 5Executive organisation design
  6. 6Scheduling
Data Strategy

After investigating the common and unique parts of the business, visualise the business with focus on the common parts. We identify the constituent elements necessary for business activities and implement data design while considering how they can be utilised as resources.

  1. 1Visualisation of operations and systems
  2. 2Overall picture based on common parts
  3. 3Organising generalised elements of common parts
  4. 4Organising generalised elements of unique parts
  5. 5Consider how to use it as a resource
  6. 6Data design that supports operations and systems

Marketing & sales. Development & operations. Security.

Every business has these three layers. We design data and IT systems so the three reinforce each other — not the typical reality where each builds its own silo and ends up duplicating work, contradicting policy, and leaking customer trust.

Marketing & Sales

Data design for revenue

  • Design for Marketing — make the location of marketing data and the evaluation method for each measure explicit.
  • Designed for Sales — secure, easy I/O for managing customer issues over the long term.
  • Customer-information protection — anonymisation, virtualisation, access logs.
3 deliverables →

Development & Operations

Data design for build and run

  • Resource & progress structure — manage tasks across the development organisation.
  • Functional + data-domain decomposition — services broken down to start conditions, I/O, end conditions.
  • Lifecycle management — visualise lineage, catalogue, retention, deletion.
  • Progress & quality reporting — milestone status, review findings, remediation tracking.
12 deliverables in full · see the yellow tube ↓

Security

Data design with security in mind

  • Regulatory compliance — comprehensive coverage of laws and guidelines.
  • Confidential-information protection — internal, external, and human-error vectors.
  • Device control — remote management, restrictions, log monitoring.
  • Trust enhancement — third-party penetration testing, regular audits.
  • Authentication & authorisation — owner / steward / approval boundaries.
⚠ Already hacked? We solve it →
Deliverables, domain by domain.
Data design in marketing and sales
Design for Marketing
The location of various marketing data and the method of evaluating measures generated by the data are clear.
Designed for Sales
The system must be able to securely and easily input and output a variety of data to manage customer issues and build long-term trusting relationships.
Design for Customer Information
Anonymising and virtualising customer information, clarifying who is allowed to see it, who is allowed to see it, and their access records.
Data design with development and operation in mind
Design for the delivery team
Establish a structure and system to manage tasks and resources in the development organisation, and a mechanism to check progress.
Design for functional requirements
The goals and functions you want to achieve with the system are expressed in a simple design and detailed blueprints.
Design for runbooks
A management system has been established to be responsible for creating / updating / notifying / ascertaining the location of manuals and data catalogues.
Design for data lineage
A system has been established to break down each service in terms of function and data domain and record creation / update / access.
Design for processing boundaries
Each service should be broken down in terms of functions and data domains, and for each function, the starting conditions, input and output data, and ending conditions should be determined.
Design for incident handling
A system has been established to receive / respond / track / improve / manage problems.
Design for knowledge
Index user and organisational know-how for easy search and management.
Design for the data lifecycle
Visualise and manage the lifecycle of data, including its lineage and catalogue.
Design for roles and responsibilities
Persons in charge, their roles, and workflows to be implemented must be organised in consideration of utilisation from the on-site perspective.
Design for data structure
Define structured and unstructured data for each type of data domain.
Design for owners and roadmaps
A responsible person and a roadmap are established for each domain, and the perspective and method for on-site performance evaluation are determined.
Design for handling rules
There is a clear business flow for registering, updating, referencing, and deleting data and functions, and information of not only customers but also employees and the company is protected.
Data design with security in mind
Design for Regulatory Compliance
The design must comply with various laws and guidelines and ensure comprehensiveness.
Designed to protect confidential information
Designed to prevent or minimise information leaks due to attacks from inside or outside the organisation or due to human error.
Designed for the device
Enable remote management of devices, restrict usage, installation, connection, and configuration changes, and monitor logs.
Designed to enhance trust
Confirm vulnerabilities through audits by third-party organisations, including penetration tests, and make regular improvements.
Authentication and authorisation design
Establish a data owner / system owner and clarify the demarcation point of responsibility for policy formulation, access approval, and quality for each domain.

For business goals

Draw up a phased design, including a transition period, to gradually move closer to business goals.

For data strategy

Maximise data as a shared resource by visualising the shared parts of each department and each job.

How we work · Plan · Do · Check · Action

Each phase has a standard support path (where most of the work lives) and a special support path for situations that need direct LV3 involvement — guidelines, audits, third-party evaluation, knowledge consolidation. The two paths run together so the engagement always has a fall-back.

P Plan
Standard
① Understand the current situation ② ASIS visualisation ③ TOBE visualisation ④ Migration plan
Special
Guidelines formulation Audit
D Do
Standard
① Hub construction ② Hub migration ③ New construction
Special
Test operation
C Check
Standard
① Responsible-party review ② Correction ③ Issue management
Special
Third-party evaluation
A Action
Standard
① User adoption ② Operation ③ Troubleshooting
Special
Accumulation of design knowledge
Questions and Answers
Q

What kind of IT-design work have you done?

A

We have led IT design across manufacturing, industrial control, medical devices, accounting, telecommunications, and military sectors. Our scope spans business → data → IT-infrastructure design, all aligned to the goals envisioned by the CEOs and executives we work with.

Q

Can you develop the IT system as well?

A

Design is where we lead — after many wins and losses, we concluded it's our core competence. When you need the build as well, we can take it on, from contract development to a PoC; and we're glad to hand off where another firm does it better.

Nine years. Across industries. The mission stays the same.

Since LV3 was founded in 2017, we have supported data projects ranging from continuous 24-hour ingestion of hundreds of millions of records, to data-magazine frameworks that span European subsidiaries, to academic-grade A.I. and optimisation work, to commercial efforts that replace intuition-and-experience decision-making with measurable evidence.

"That is what our business stands for." Our clients are constantly confronted with major problems. We implement value creation through IT design — not only through numerically measurable business growth, but also by shaping a new working relationship between management and the field. The methodology behind these nine years is collected in the book ITG (Gijutsu-Hyoron, 24 August 2026).

Projects we've supported.
Project for a QR-code payment provider
A QR payment provider
Project for a property & casualty insurer
A P&C insurer
Project for a pharmaceutical company
A pharmaceutical company
Project for an automotive manufacturer
An automotive manufacturer
Project for a semiconductor manufacturer
A semiconductor manufacturer
Project for a medical-device manufacturer
A medical-device manufacturer
Project for an apparel company
An apparel company
Project for a marine shipping company
A marine shipping company
Project for a general trading house
A general trading house
Project for an internet service provider
An internet service provider
Project for the public sector
The public sector
Project for an international airport operator
An international airport operator

Confront emergencies with the power and expertise of IT Design.

LV3 was founded with the belief in the power of IT to protect the safety and order of society.

With a sense of mission born of the founder's experience, we use IT design and technology to confront major social problems.

Although the people who do this work have no special abilities, they carry out their mission as modern-day "heroes" by protecting social systems through IT.

Lighthouse

Click here for consultation
on IT-design support.

One LV3 consultant. One project. The roadmap and the data model — drawn from the destination back, executed alongside your team.

Engagement modes, flow, and procurement checklist: see how we work.