Translating a website from a business model to a site structure
Offerings, target groups, decision-making processes, and operational responsibilities are translated into page types and relationships, instead of displaying the organizational chart as a menu.
For website managers and UX teams, "From Business Model to Page Structure" can be assessed primarily based on two aspects: "Value Proposition" and "Organizational Chart Navigation." This comparison makes the professional boundaries tangible.
Published: 3 min read · Author: Sebastian Geier
How does a user-oriented website structure emerge from a business model?
The starting point is the tasks, problems, and decision-making steps of the target groups. Internal products and responsibilities are assigned to these processes; they determine maintenance responsibilities, but not automatically the visible structure.
Value Proposition
Value Proposition – Each key area explains for whom which condition is being improved and how the offering differs from alternatives.
Decision-Making Process – Content answers successive questions from initial orientation to selection, trust, and the next binding step.
Care Assignment – Internal responsibility is defined for each page type without departmental boundaries visibly interrupting the user journey.
Organizational Chart Navigation
Organizational Chart Navigation – Users must understand internal department names before they can categorize a problem or a suitable service.
Unconnected Offers Product pages describe services individually, but do not lead to a reasoned decision based on need and comparison.
Responsibility Gap – A user-centric hub spans multiple teams without anyone consistently maintaining its content and transitions.
Care Assignment
Central user questions without a clear objective, and pages that only explain an internal unit instead of demonstrating value.
Drop-offs or redirects at transitions between orientation, offer comparison, trust verification, and next action.
Decision-Making Process
Value propositions, target group tasks, and crucial questions are initially collected independently of existing pages and departments.
From this, recurring page types, central hubs, and necessary transitions for orientation, comparison, and action are modeled.
Existing content and internal owners are then mapped to the target model, merged, or marked as gaps.
Working Example: "Organizational Chart Navigation"
A company doesn't organize its website according to three internal teams, but rather according to the tasks of planning, implementation, and operation. Offer pages remain assigned to the responsible teams, but shared hubs guide users to the appropriate decision without requiring knowledge of this organizational structure.
Related questions and next steps
An in-depth question answered Identifying structural dead ends in large websitesHow do you find pages that don't provide users and crawlers with a meaningful structural path?
Further Perspectives Using Click Data to Identify Weak Internal Paths.
If you want to practically implement "From Business Model to Page Structure," you can refer to Robust Website Systems This focuses on "Page Types and Content Model" and "Value Proposition."
Conclusion: From Business Model to Page Structure
The business model provides value propositions and responsibilities, but not yet a user structure. Only the translation into tasks and decisions creates a viable website architecture.
Sources and Further Information
The following official documentation and standards provide the technical classification.
Organize and group GOV.UK contentThe official GOV.UK guidance describes user-related content groups, naming conventions, and hierarchies, rather than organization-driven filing.
Learning about users and their needs – GOV.UK Service ManualThe guideline justifies observed tasks and needs as the starting point for structural decisions. ...2: The primary sources define the professional framework for "Creating a binding content map."
Key Thesis
First, the value propositions, tasks, and decision-making steps of the target groups are modeled. This results in clear page types, hubs, and connections; internal departments determine responsibilities, but not automatically the user journey.
What This Is Not About
A website should neither replicate the organizational chart nor include every internal product as a standard main menu item.
What it's about
It translates value propositions and user decisions into page types, hubs, and clear transitions.
Information Architecture & Taxonomy
When a hub page has real structural value
As a separate step in "From Business Model to Page Structure," the question is: What function must a hub page fulfill so that it is more than just a list of links?
Information Architecture & Taxonomy
Information architecture for websites with many regions
Supplements "From Business Model to Page Structure" with a separate decision: How does a website structure scale across many regions without interchangeable page copies?
Insights Overview
All VELUNO Insights at a Glance
Further analyses on Website Systems, digital visibility, and robust working models.
Decision Path: Practical Next Step
A target audience and a key value proposition can be modeled as the first complete path. Existing pages are then evaluated not by department, but by their contribution to this path.