Work in Progress: Show the Build Before It Behaves
Welcome to Build Logs → Work in Progress — the place to share projects while they are still unfinished, slightly messy, half-polished, confusing in one corner, and possibly making strange noises behind the settings page.
This is not the launch stage.
This is the workshop stage.
The place where you can say:
It works.
Mostly.
Please do not click that one button yet.
That is normal.
Every finished project was once a suspicious-looking work in progress pretending it had a plan.
What this section is for
Use Work in Progress when your project is not finished yet, but you want to show what exists so far.
Good WIP posts include:
- Early website designs
- App screens
- Game prototypes
- Forum layouts
- Tool dashboards
- Landing page drafts
- Logo concepts
- UI ideas
- Feature previews
- Script setup progress
- AI workflow experiments
- Content structure drafts
- Marketplace/product ideas
- Anything still being built
A Work in Progress post does not need to be perfect.
That is the point.
This is the section for:
Here is what I have so far.
Here is what works.
Here is what does not.
Here is what I am trying to improve next.
Very useful.
Slightly exposed.
Good builder behaviour.
Work in Progress template
Copy this:
Project name:
What I am building:
Current stage:
What works so far:
What is unfinished:
What feels rough:
What I need feedback on:
Screenshots/link:
Next step:
Example:
Project name:
Fyrbloc
What I am building:
A builder community for creators, coders, designers, indie developers, AI users, and digital makers.
Current stage:
Early foundation and content setup.
What works so far:
Tags, starter posts, profile fields, announcement areas, rules, thumbnails, and basic community structure.
What is unfinished:
More section templates, branded thumbnails, onboarding polish, and more real member activity.
What feels rough:
Some image placeholders are temporary and a few sections still need stronger examples.
What I need feedback on:
Whether the forum structure feels clear for new members.
Screenshots/link:
https://fyrbloc.com
Next step:
Create more templates for Launches, Resources, Site Reviews, and Marketplace.
That is a solid WIP post.
It shows the build without pretending everything is finished.
Honest beats polished fog.
What counts as Work in Progress?
Early layout
I have the homepage structure, but the wording needs work.
Good WIP post.
Show it.
Ask what is unclear.
Broken-but-visible feature
The dashboard loads, but the save button does not work yet.
Good WIP post.
Mention the broken bit before someone finds it and feels clever.
Design direction
I am testing three logo styles and need feedback on which one fits best.
Good WIP post.
Add images.
Expect opinions.
Possibly too many.
Game prototype
The player can move, enemies patrol, but combat still feels like two shopping trolleys arguing.
Excellent WIP post.
Very clear.
Very concerning.
Tool or script setup
The install works locally, but I still need to clean up the setup guide.
Good WIP post.
Mention what is ready and what is missing.
WIP posts are allowed to be messy
This section exists because builders often wait too long before sharing.
They think:
I will post it when it is finished.
Then the project quietly enters the swamp.
The WIP section helps avoid that.
Post earlier.
Show the rough version.
Get feedback before you spend three weeks polishing the wrong thing.
Painful truth:
A rough project with feedback usually improves faster than a hidden project with perfect intentions.
The hidden project may feel safe.
It is also sitting in the dark wearing a hoodie.
Useful WIP update types
1. The early preview
Here is the first version of the homepage.
I mostly need feedback on the headline and layout.
2. The feature preview
Here is the new profile page.
The fields work, but the layout still needs polish.
3. The design choice
I am choosing between these three colour directions.
Which feels strongest for the project?
4. The “this works but looks bad” post
The feature works.
The design looks like it lost a fight with a spreadsheet.
Feedback welcome.
5. The “I need direction” post
The idea works, but I am not sure what to focus on next.
Should I improve the homepage, add user profiles, or create starter content first?
These are all good WIP posts.
They help people reply with useful advice.
What feedback should you ask for?
Be specific.
Instead of:
Thoughts?
Try:
Does the homepage explain the project clearly?
Which logo direction feels strongest?
Does the mobile layout look usable?
Is the main button clear enough?
Would you understand what to do next?
Does this feature feel useful or unnecessary?
What should I fix before launch?
Specific questions get better replies.
Vague questions get a fog cloud with opinions in it.
Nobody needs more fog.
Good WIP screenshots
Screenshots are very useful here.
Add screenshots of:
- Homepage drafts
- App screens
- Admin panels
- Mobile layouts
- Feature previews
- Error screens
- Game scenes
- Logo options
- Colour tests
- Before/after changes
- Roadmaps
- Wireframes
- Settings pages
Before posting, hide private info:
Passwords
API keys
Tokens
Private emails
Customer data
Payment details
Server login details
Private documents
A screenshot should show the work.
Not your secrets.
Secrets are not design assets.
Good WIP title examples
Use titles like:
WIP: First Homepage Draft for My Booking Tool
WIP: Testing a New Dashboard Layout
WIP: Early Game Prototype With Basic Enemy Movement
WIP: Logo Concepts for My New Project
WIP: Forum Structure Before Launch
WIP: AI Workflow Tool — First Usable Version
Avoid:
Update
Progress
Thing
Some stuff
Those titles need a nap.
Tell people what the post is about.
Replying to Work in Progress posts
Good replies are direct and useful.
Helpful replies:
The idea is clear, but the first section needs a stronger one-line explanation.
The layout works on desktop, but mobile spacing needs another pass.
The second logo is easier to read at small size.
The feature makes sense, but I would remove the extra settings until launch.
This is good enough for a small test launch. Fix the broken button first.
Less helpful replies:
Looks bad.
Wrong stack.
Just rebuild it.
Nobody will use this.
No.
Critique the build.
Do not throw a brick at the builder.
This is Fyrbloc, not a comment section under a cursed video.
The WIP honesty rule
When posting, be honest about the state of the project.
Good:
This is early and not mobile-ready yet.
Good:
The main flow works, but the design is unfinished.
Good:
This is a concept, not a live product yet.
Bad:
Fully launched platform.
when it is actually:
One page, one button, and a dream.
No need to fake it.
Work in Progress is allowed to be unfinished.
That is literally the label.
WIP checklist before posting
Before posting, check:
Did I explain what the project is?
Did I say what stage it is at?
Did I list what works?
Did I list what is unfinished?
Did I say what feedback I want?
Did I include screenshots or a link if useful?
Did I hide private information?
Did I mention the next step?
That is enough.
Do not overthink it.
Post the thing before you redesign the thing before posting the thing.
That loop is dangerous.
Mini WIP challenge
Post a Work in Progress update using this:
Project:
Current state:
One thing that works:
One thing that looks rough:
One thing I need feedback on:
One thing I will fix next:
Example:
Project:
A small landing page builder.
Current state:
Early prototype.
One thing that works:
Users can create a basic page.
One thing that looks rough:
The editor sidebar is too cramped.
One thing I need feedback on:
Does the editor layout make sense?
One thing I will fix next:
Mobile preview.
Clean.
Useful.
No unnecessary drama.
Only the normal amount of builder drama.
Final note
Work in Progress is where projects become visible before they become finished.
Show the rough version.
Ask focused questions.
Accept useful feedback.
Fix the next thing.
Keep moving.
A finished launch is built from messy previews, awkward drafts, tiny fixes, and brave little posts that say:
Here is what I have so far.
That is enough.
Build. Show Early. Improve. Launch.
