The Big Question; If the Website Is the Centre, How Should It Be Organised?
________________________________________
Introduction
Imagine entering a large hospital.
You are not interested in the building.
You simply want to find the right doctor.
Now imagine the receptionist saying,
"Our hospital has 427 rooms.
Please explore."
You would probably walk away.
Instead, hospitals are organised around people's needs.
Emergency.
Cardiology.
Orthopaedics.
Paediatrics.
Radiology.
Everything is arranged to help people find answers quickly.
A website should work exactly the same way.
Visitors do not come to admire your menus.
They come because they have a question.
The easier you answer that question, the more useful your website becomes.
________________________________________
3.1 Stop Thinking About Pages
One of the biggest mistakes organisations make is asking,
"How many pages should our website have?"
That is the wrong question.
Instead ask,
"What questions should our website answer?"
A hundred-page website can still be confusing.
A twenty-page website can be incredibly useful.
The difference is not the number of pages.
The difference is how knowledge is organised.
________________________________________
3.2 Organise Around Questions, Not Departments
Most organisations design websites around themselves.
Typical menus look like this:
- Home
- About Us
- Products
- Services
- Gallery
- Contact Us
There is nothing wrong with these pages.
But ask yourself one question.
Does a customer wake up in the morning thinking,
"I want to visit the About Us page."
Almost never.
Customers think differently.
They ask:
- Which product is suitable for me?
- How much will it cost?
- What is the difference between these two options?
- Can I trust this company?
- Has someone else used it?
- What mistakes should I avoid?
That is how websites should be organised.
Around customer curiosity.
Not organisational departments.
________________________________________
3.3 Every Website Needs Knowledge Domains
Think of your website as a well-organised library.
Instead of hundreds of unrelated pages, create a few major knowledge domains.
For a food company, these might be:
- Ingredients
- Nutrition
- Processing
- Recipes
- Buying Guides
- Food Safety
- Storage
- Consumer Questions
For an agriculture company:
- Crops
- Soil
- Seeds
- Irrigation
- Plant Protection
- Farm Machinery
- Market Information
- Farmer Stories
Each knowledge domain then grows naturally over time.
________________________________________
3.4 Every Domain Should Answer Questions
Now imagine entering the
"Soil"
section.
Instead of showing only products,
the visitor immediately sees questions like:
- What makes soil fertile?
- Why does soil lose productivity?
- How do I improve soil health?
- What is the difference between compost and vermicompost?
- How much organic matter is enough?
Every question leads to an answer.
Every answer may connect to:
- Stories
- Videos
- Images
- FAQs
- Case Studies
- Downloads
- Products
- Research
Knowledge begins to flow naturally.
________________________________________
3.5 The Journey Should Feel Natural
Good websites do not force people to search repeatedly.
They gently guide them.
Imagine someone reading:
"Why do spices contain pesticide residues?"
After finishing the article, the website could naturally suggest:
- How are spices tested?
- How should spices be stored?
- Which spices have the highest residue risk?
- Common myths about pesticide-free spices.
- How to choose reliable spice brands.
Every answer creates another question.
Every question keeps the visitor learning.
That is exactly what a good teacher does.
________________________________________
3.6 Think Like a Librarian, not a Designer
This may be the most important lesson in this module.
Many websites are designed beautifully.
But they are difficult to use.
A good librarian does not ask,
"How beautiful are my bookshelves?"
Instead,
they ask,
"Can people find the book they need within two minutes?"
Exactly the same principle applies here.
Good knowledge architecture is invisible.
People simply find what they need.
________________________________________
Did You Notice?
A website is not a collection of pages.
It is a collection of answers.
The pages are only containers.
The real value lies in the knowledge inside them.
________________________________________
A Simple Knowledge Architecture
Instead of this...
Home
About Us
Products
Gallery
Contact
Think like this...
HOME
↓
Knowledge Domains
↓
Questions
↓
Answers
↓
Stories
↓
Case Studies
↓
Downloads
↓
Tools
↓
Products & Services
↓
Contact
Notice something interesting.
The products appear almost at the end.
Not because they are unimportant.
Because customers trust organisations that first help them understand.
________________________________________
3.7 Every Organisation Will Have a Different Architecture
A school will organise knowledge differently from a hospital.
A food company will organise knowledge differently from a law firm.
A tourism website will look different from a manufacturing company.
The architecture should always reflect the questions that customers ask most frequently.
There is no universal menu.
There is only a universal principle:
Organise knowledge the way customers think.
________________________________________
Module Summary
A Knowledge Hub is not built by adding more pages.
It is built by organising knowledge in a way that helps people—and AI systems—find answers quickly and confidently.
The best websites are not those with the most information.
They are the ones where people never feel lost.
________________________________________
Assignment
Choose the same organisation you selected in the previous modules.
Forget its existing website for a while.
Instead, imagine you are building it from scratch.
Answer these questions:
- What are the eight to ten biggest questions customers ask?
- What Knowledge Domains naturally emerge from those questions?
- What information belongs under each Knowledge Domain?
- Which stories, videos, case studies, FAQs and downloads can support each domain?
- Can you draw a simple map showing how a visitor would move from a question to an answer and then to related knowledge?
Congratulations.
You have just taken the first step from designing a website to designing a Knowledge Hub.
