The fastest way to make Conejo feel complicated is to start with the wrong shape. Most teams do not need every feature on day one. They need the right starting point. In practice, that usually means choosing between three things: a simple survey, a chain, or a dashboard.

Start with the job, not the object

Each format is good at a different kind of job:

• Use a survey when one prompt or one short response flow is enough.
• Use a chain when the next question should depend on the answer that just came in.
• Use a dashboard when the main goal is reviewing results from one or more surveys or chain steps in a shared view.

The mistake teams make most often is using a chain when a survey would be cleaner, or trying to turn a survey detail page into the dashboard they really need.

A good rule of thumb: collect with a survey or chain, then review with a dashboard when the team needs a broader operating view.

When a simple survey is the right choice

Choose a survey when the response should be fast, direct, and easy to distribute. A simple survey works best when everyone sees the same question or short sequence and the team does not need branching logic to make the experience useful.

Simple surveys are a strong fit for:

• one-question event or workshop pulses,
• quick customer satisfaction checks,
• embedded prompts inside a product or portal,
• standalone feedback links and QR handoffs.

If the answer only needs one question, do not overbuild it. A clean survey is often the fastest route to better completion.

When a chain is the better fit

Choose a chain when the second question should change based on the first answer. Chains are what make Conejo feel like a guided workflow instead of a flat form. They are especially useful when different response bands need different follow-up or when several linked steps should behave like one shareable experience.

Chains are a strong fit for:

• NPS or score-based follow-up,
• meeting and workshop feedback with different second questions,
• flows where each respondent should only see the next useful step,
• one route, one QR code, and one presenter flow across multiple steps.

If the response path should adapt, a chain will usually be cleaner than forcing every respondent through the same survey structure.

When a dashboard is the real need

Choose a dashboard when the collection flow already exists and the next problem is how the team should review the results. Dashboards are not for asking better questions. They are for pulling together charts, KPI cards, response feeds, and aggregates from one or more sources into a single operating view.

Dashboards are a strong fit for:

• combining multiple surveys into one live view,
• mixing survey-level and chain-step data in one place,
• building reviewer views for internal teams or client portals,
• creating an aggregate row plus focused widgets for ongoing review.

If the question is “how should people review this?” rather than “what should we ask next?”, a dashboard is often the better answer.

How the three usually work together

These formats are not competitors. Most teams end up using them together:

• a survey for the simple entry point,
• a chain when the flow needs branching or guided follow-up,
• a dashboard for the team reviewing patterns and deciding what happens next.

That is the normal Conejo shape. Collection happens in surveys and chains. Review happens in dashboards.

Decision shortcuts

If you are deciding quickly, use this filter:

• One question or one fixed path? Start with a survey.
• Different respondents need different next questions? Start with a chain.
• The team needs one place to review several data sources? Build a dashboard.
• You need both guided collection and shared review? Use a chain plus a dashboard.

Common mistakes to avoid

• Using a chain for a single-question prompt. That adds complexity without helping the respondent.
• Keeping everything inside one survey when branching is clearly needed. The follow-up becomes generic and less useful.
• Expecting a dashboard to solve a bad question design. Dashboards improve review, not collection logic.
• Building too much too early. Start with the smallest shape that does the job well.

Where to go next

Once you know which shape fits, the next step is usually more specific: a QR-code workflow for events, a score-based chain for guided follow-up, or a custom dashboard that combines several sources into one live review surface. The right starting point makes every later decision easier.