Enterprise Systems
Grendene — ERP Evolution
Working across requirements, integrations, development and testing in the evolution of an internally developed ERP ecosystem.
Experience across requirements, integrations, development and testing in the evolution of an internally developed ERP ecosystem.
- Role
- Business / Systems Analysis
- Focus
- Requirements · Integration · Development · Testing
- Period
- 2014 — 2019
The context
Before Product Management, there was technology.
Grendene represents an important part of João's technical foundation, working directly with enterprise systems and the connection between business requirements and software implementation.
My role
Analysis and evolution of an internal ERP.
João worked in the analysis and evolution of an internally developed ERP, covering requirements, integrations, development and testing.
Requirements
Translating business needs into system requirements.
Integration
Connecting the ERP with other systems.
Development
Working close to software implementation.
Testing
Validating that solutions behaved as required.
Product foundation
Why this experience still matters
Working close to software implementation created a technical foundation that later became valuable in Product Management: understanding constraints, asking better technical questions and connecting business needs to feasible solutions.
What I learned
Three professional takeaways.
Understanding constraints improves product decisions.
Knowing how systems are built makes trade-offs clearer.
Requirements are a bridge, not a handoff.
Good requirements connect business intent with implementation.
Enterprise systems are products too.
Internal tools deserve the same rigor as customer-facing products.
The takeaway
Technical depth makes product thinking more grounded.
Grendene is the technical foundation behind the product work that followed.