How I Work

Hi, I’m Fidaa 👋
I build things — mostly web apps, dashboards, and experimental products.
This is a quick look at how I think, plan, and execute my work.

I Start With Clarity

Before building anything, I don’t jump straight into the product.

I try to understand the bigger picture first:

What problem are we actually solving?
How does the business flow work in real life?
What are the operational steps behind it?
What are the expectations from the business side?

I focus a lot on aligning with the client’s expectations — not just building features, but making sure the product actually fits how things work in the field.

After that, I define a main goal (similar to Objectives and Key Results, but in a simpler way), and break it down into smaller, achievable targets.

I Plan in Phases

My planning style is structured but still practical.

Instead of planning everything at once, I usually break things into phases:

Phase 1 → initial / core features
Phase 2 → improvements / extensions
Phase 3 → refinements

Each phase is divided into smaller goals (mini targets), and:

Each goal has its own estimation
Usually mapped into weekly targets

This helps:

Keep progress measurable
Align expectations between developer and client
Avoid overpromising too early

I keep planning simple, but intentional.

I Work in Weekly Cycles

I treat each week like a small sprint (inspired by Scrum):

Focus on a few important tasks
Deliver small, consistent progress
Adjust based on real conditions

I don’t aim for perfect execution — I aim for steady progress.

I Align Early With Others

When working with a team or client, I prefer:

Sharing plans early
Syncing expectations at the beginning
Adjusting based on feedback

I believe early alignment prevents bigger problems later.

Deadlines & Responsibility

I take deadlines seriously, but I also stay realistic.

If something is off track:

I communicate it early
I adjust the plan transparently

I prefer being clear and honest rather than forcing unrealistic timelines.

Communication Style

I prefer starting with written communication.

I use text (chat/docs) for initial discussion
I write down context and key points before any meeting

If the topic becomes complex or unclear:

Then I move to a quick online meeting

This way:

Meetings stay focused
We only discuss what actually needs clarification
Time is used more efficiently

Always Improving

I don’t follow rigid frameworks.

But I continuously try to:

Improve how I understand problems
Improve how I plan and execute
Learn from each project

In Short

I focus on understanding the business, not just the product
I plan in phases, not all at once
I work in small, consistent steps
I value clarity, alignment, and realistic execution