0 of 20 answered 0%
TAKSHNI Production CRM — Discovery Interview
Factory Incharge: Krishna Mahiwal
Metallurgical Engineer & Production Head

This interview captures hidden production scenarios that will shape the design of Takshni's new production CRM. There are no right or wrong answers — the goal is to understand the real complexity of the factory floor. Please answer as honestly and in as much detail as possible. All responses are saved directly to the system.

Interviewer details
1
Rework, scrap & failure
The biggest hidden gap
Q 01 Jab ek piece QC mein fail ho jata hai — kya hota hai? Kya use dobara banate hain (rework), ya poora scrap kar dete hain? Aur agar rework karte hain, toh wo kis stage pe wapas jata hai?
Why this matters: A linear progress bar can't model a piece going backwards. If pieces loop back, the lifecycle model must support rework loops — not just forward movement.
0 characters
Q 02 Jab brass scrap hota hai, kya wo metal recycle/remelt hota hai? Uska weight aur cost kaise track karte ho?
Why this matters: Scrap metal often re-enters the material pool. This affects material accounting — you can't just deduct stock, you may need to add scrap back.
0 characters
Q 03 Ek casting mein kitne percent pieces pehli baar mein sahi bante hain? Yield kya rehta hai average?
Why this matters: If first-pass yield is 60%, planning must account for making extra pieces. The system needs "quantity attempted vs quantity passed."
0 characters
2
Batching & shared processes
One stage, many pieces
Q 04 Kya aap ek time pe kai pieces ek saath banate ho — jaise ek hi furnace mein 5 pieces ka metal pour? Ya har piece alag banta hai?
Why this matters: If multiple pieces share a single pour, time and cost are shared across pieces — not per piece. This fundamentally changes how the system attributes time and cost.
0 characters
Q 05 Agar ek bespoke order mein 3 identical pieces hain (jaise hotel ke liye 3 same sculptures), toh aap unhe ek order maante ho ya teen alag?
Why this matters: Determines whether an order can contain multiple units. Large hospitality projects may need 10–50 identical pieces — the data model must handle this.
0 characters
3
Materials & outsourcing
Beyond simple stock
Q 06 Kya koi stage bahar (outside vendor) karwate ho — jaise electroplating, polishing, ya powder coating? Us bahar gaye kaam ko kaise track karte ho?
Why this matters: Outsourced stages have transit time and vendor delays. The system needs an "out for job-work" status — a common blind spot that causes untracked delays.
0 characters
Q 07 Kya kabhi ek hi material ka quality batch-to-batch alag hota hai? Jaise ek supplier ka brass doosre se alag behave karta hai casting mein?
Why this matters: If material quality varies, you may need batch/lot tracking — linking a defect back to a specific material batch. Critical for root-cause analysis.
0 characters
Q 08 Kuch raw materials ka lead time kitna hota hai? Koi material aisa hai jo order karne ke baad weeks lagte hain aane mein?
Why this matters: Long-lead materials must be ordered before production planning. The reorder-alert logic needs lead time, or alerts will fire too late.
0 characters
4
Artisans & dependencies
Multi-location reality
Q 09 Artisans alag-alag states mein hain (Kashmir, Bastar, Odisha). Kya ek piece kai jagah travel karta hai bante waqt? Ya sab ek hi jagah hota hai?
Why this matters: If a piece physically moves between cities during production, you need location tracking and inter-city transit time built into the lifecycle.
0 characters
Q 10 Kya kuch artisans seasonal hain — jaise festival ya kheti ke time available nahi rehte? Capacity planning mein ye factor karna padta hai?
Why this matters: Artisan availability isn't constant. Harvest season, festivals, and family obligations affect capacity — the planning module may need an availability calendar per artisan.
0 characters
Q 11 Agar ek hi artisan teen orders pe kaam kar raha hai, toh priority kaise decide hoti hai? Kaun pehle?
Why this matters: Reveals whether you need an order-priority concept. Bespoke client deadlines often jump the queue over stock pieces — the system must support reprioritisation.
0 characters
5
Client-driven changes
The bespoke wildcard
Q 12 Bespoke orders mein, kya client beech mein design change maangta hai? Ya approval ke liye photo bhejni padti hai bich-bich mein? Wo kaise handle karte ho?
Why this matters: Mid-production approvals and design changes are a major delay source. The system may need a formal "client approval" stage that pauses the clock.
0 characters
Q 13 Kya kabhi order hold ya cancel ho jata hai bich mein? Tab us piece aur material ka kya hota hai?
Why this matters: Orders don't always complete. The system needs "on hold" and "cancelled" states, plus a way to track partially-made inventory.
0 characters
6
Costing & payments
Often the real business need
Q 14 Kya aap har piece ki actual cost track karna chahte ho — material + labour + outsourcing? Ya sirf time aur production track karna hai abhi ke liye?
Why this matters: Costing is often the unstated goal. If Takshni wants to know the true cost and margin of each piece, the data model must capture cost at every stage from day one.
0 characters
Q 15 Client se payment milestones hote hain? Jaise advance, mid-payment, delivery pe balance? Kya production status ko payment se link karna useful hoga?
Why this matters: Linking production milestones to payment triggers is high business value. Reveals whether this needs a sales/finance layer or stays purely production-focused.
0 characters
7
Process variation & edge cases
The "it depends" zone
Q 16 Kya har baar ek hi product ka process flow same rehta hai? Ya kabhi-kabhi stages skip ho jaate hain ya extra add hote hain?
Why this matters: If process flows vary per instance, you can't lock a rigid template. The system needs flexible, editable flows per order — not one fixed template per product type.
0 characters
Q 17 Drying, curing, ya cooling jaise koi stage hai jahan piece bas wait karta hai — koi active kaam nahi hota? Use time mein count karte ho?
Why this matters: "Wait time" is real elapsed time but zero labour. The system must distinguish active work time from passive wait time — otherwise time analytics will be misleading.
0 characters
Q 18 Saal ke kaunse mahine sabse busy rehte hain? Kya production ka koi peak season hai jab orders zyada aate hain?
Why this matters: Seasonality affects capacity planning and helps prioritise when the system must be most robust — steady flow or handling order surges.
0 characters
Q 19 Abhi jo Excel use kar rahe ho — usme aisa kya hai jo aap zaroor naye system mein chahte ho? Aur aisa kya hai jo bilkul kaam nahi karta?
Why this matters: Reveals which habits to preserve and which pain points are most acute. Understanding the current Excel reveals hidden logic that must be replicated or improved.
0 characters
Q 20 Agar koi ek cheez aaj raat ko magic se theek ho jaye production mein — toh wo kya hogi? Sabse zyada dard kahan hai?
The most important question: Cuts through feature lists to find the emotional core problem. Whatever Krishna says here should be the very first thing the MVP nails.
0 characters
+
Interviewer's additional observations
Notes Any other observations, quotes, or scenarios that came up during the interview that aren't captured above?

Please review all answers before submitting. Once submitted, the response is saved to the server and cannot be edited. Ensure the interviewer name and date are filled in.

✓

Interview saved successfully

All responses have been recorded. The production team can now review this interview in the admin panel. Thank you for your time, Krishna.