What is worth developing — and what is not?

Why projects get stuck

Many projects fail not because of missing data, regulations or market analysis —
but because the wrong question is asked too early.

Before asking “what is allowed” or “what sells”, there is a more fundamental one:

Why should this project exist at all — here, in this form, and now?


My role

I work at the earliest and most uncertain stages of a project —
when directions are still open, constraints conflict, and it is not yet clear which path is worth committing to.

My focus is not detailed design or formal approvals.
My focus is clarifying intent, identifying viable scenarios, and finding non-obvious ways forward.

I help clients:

  • understand what they are really trying to achieve
  • see alternative directions instead of a single assumed solution
  • identify conflicts and risks early, before they become expensive
  • decide what is worth developing — and what is not

Before market studies and permits

Market research, feasibility studies, and regulatory checks are essential —
but they work best after the project’s core logic is clear.

I often work before:

  • highest & best use analysis
  • market positioning
  • permit strategies

My role is to frame the right questions and define meaningful directions —
so that market consultants and local specialists can test something that actually makes sense.


Working with local expertise

All regulatory, permitting and compliance matters are validated with local professionals —
architects of record, permit consultants, engineers or legal advisors — depending on the project.

I do not replace local expertise.
I integrate it into a coherent strategy.

This division of roles allows projects to move forward with clarity, realism and reduced risk.


How I usually work

  • short, focused involvement at the beginning
  • exploration of 2–3 realistic scenarios
  • clear articulation of risks, constraints and trade-offs
  • definition of next steps and decision points

Further involvement is optional and intentional —
not automatic and not operational.


Who this is for

This approach is useful when:

  • a project feels blocked or contradictory
  • the obvious solution does not feel right
  • the object, site or context resists standard answers
  • there is uncertainty about direction, not execution

If you already know exactly what to build and just need drawings —
you probably don’t need me.

Комментарии

Один комментарий на ««What is worth developing — and what is not?»»

  1. Аватар пользователя Комментатор WordPress

    Привет! Это комментарий.
    Чтобы начать модерировать, редактировать и удалять комментарии, перейдите на экран «Комментарии» в консоли.
    Аватары авторов комментариев загружаются с сервиса Gravatar.

Добавить комментарий

Ваш адрес email не будет опубликован. Обязательные поля помечены *