
Sign up to save your podcasts
Or


In many R&D projects, especially in printed electronics, there is a moment when you are expected to test something that does not yet exist. There is no finished component, nothing to physically connect, nothing you can press or measure in a standard way. And yet, decisions must be made, budgets must be managed, and the project needs to move forward. This is exactly the point where testing stops being just a phase at the end of the project and becomes a fundamental part of how the entire development process is built.
This material comes from the free LCE Insider newsletter, available in both English and Polish.Subscribe today! https://lcelektronik.com/lce-insider/?utm_source=&utm_medium=&utm_campaign=podcastIf you have any question don't hesitate to contact us https://lcelektronik.com/kontakt/?utm_source=&utm_medium=&utm_campaign=podcast
In many R&D projects today, there is one question that is rarely asked directly, but has a huge impact on the outcome. Are you working with a supplier, or with a real partner?
At first, the difference may seem small. Both deliver something. Both are part of the project. But when the project becomes complex, when time pressure increases, and when unexpected problems appear, this difference becomes very clear.
A subcontractor focuses on execution. They receive a brief, complete the task, and deliver what was requested. This works well when everything is predictable. But in R&D projects, things are rarely predictable.
A partner works differently. A partner does not only execute. A partner thinks with you. They try to understand not only what you want to build, but also why you want to build it. They look at the bigger picture, including business goals, technical limits, and project risks.
And this changes the dynamic of the whole project
When many managers hear the phrase “digital transformation,” they immediately imagine something big, expensive, and risky. They think about new production lines, large investments, long implementation times, and the possibility of disrupting daily operations. It often feels like something reserved only for large corporations with huge budgets. But in reality, transformation does not have to look like this. It does not need to be a revolution. Sometimes, it starts with one small, well-designed step that proves change is possible without turning the whole organization upside down.
A guide for Project Managers who want to innovate without chaos
MVP is just the beginning – not a time to celebrate
Imagine you just finished a sprint where your team built the first working prototype of a new device – light, flexible, with backlighting and touch. The client is excited. The MVP works. But now comes the real challenge: how do you move from this test version to full production without losing control over quality, costs, or schedule?
This is exactly the question that Polyend, a music gear company from Poland, asked when designing their next-generation controller. Their goal was to make something functional, light, nice-looking, and strong. The MVP came quickly – thanks to printed electronics. But moving to production needed a new approach.
This guide takes you through the most important steps of that process. We’ll show you how to avoid common mistakes, keep control even as scale grows, and learn from each sprint. This is not theory – it’s a real map based on actual projects.
This material comes from the free LCE Insider newsletter, available in both English and Polish.Subscribe today! https://lcelektronik.com/lce-insider/?utm_source=&utm_medium=&utm_campaign=podcast
Imagine you're in the middle of a sprint. Your team is finishing the design of a new user interface for a medical device. The client wants it light, modern, with touch and lighting in one panel. Someone at the daily meeting asks, “Can we use printed electronics for this?” Silence. One person says, “We don’t have time.” Another says, “We don’t know how to test it.” You – as the PM – need to decide.
Sounds familiar? That’s why we created this checklist. Not to convince you to use one specific technology, but to help you ask the right questions – to yourself, your team, and your partners. A good decision is based on facts, not guesses.
This material comes from the free LCE Insider newsletter, available in both English and Polish.Subscribe today! https://lcelektronik.com/lce-insider/?utm_source=&utm_medium=&utm_campaign=podcast
In IoT device design, every decision is a trade-off between size, function, and speed. Imagine Michał, an experienced engineer working on a new version of a diagnostic wristband. The client wants it light, waterproof, and as clean as possible—no visible complexity, no bulky parts, no cable mess inside the housing. Michał tries to solve it with classic PCBs, wires, and separate plastic panels, but the more he adds, the bigger the problem becomes: more connectors, more assembly steps, more failure points, and less freedom to shape the product the way the user actually needs it.
This is where printed electronics changes the logic of the project. Instead of building electronics as a rigid “block” and then connecting everything around it, you can printr functional layers directly on flexible substrates and integrate multiple functions into one structure. In practice, it means you can combine the HMI interface, sensors, graphics, and conductive connections in a single printed layer—thin, light, and ready to be integrated into the device housing. It’s not future tech or a lab experiment. Smart engineering teams already use it to build faster, with fewer parts, and with more control over quality and repeatability.
Project managers usually like innovation—until it brings extra risk, extra meetings, and extra uncertainty. And printed electronics can trigger exactly that reaction, especially if your team has built its experience around classic PCBs and standard components. So let’s walk through the five most common concerns PMs have about printed electronics, and how to solve them in a practical, low-risk way.
This material comes from the free LCE Insider newsletter, available in both English and Polish.Subscribe today! https://lcelektronik.com/lce-insider/?utm_source=&utm_medium=&utm_campaign=podcast
When you design an IoT device, you often fight the same battle every time: you need more functions in less space, the product must stay light and cost-effective, and assembly should be fast and repeatable. In many cases, the biggest “space and complexity” generator is the traditional PCB, together with connectors, wires, and mechanical mounting.
That’s why more and more designers ask a simple question: do we really need a classic PCB here, or can we print the circuit instead? Printed electronics is a method of creating electronic layers by printing conductive, insulating, sensing, or protective inks on flexible materials.
Instead of building a rigid board and then connecting everything around it, you can build thin, lightweight circuits directly on substrates like PET film, TPU, paper, fabrics, or even biodegradable foils. The result is an electronic layer that can be integrated into the surface of the product, into the housing, or into an HMI panel, which makes printed electronics especially attractive for IoT, wearables, automotive, and medical devices.
This material comes from the free LCE Insider newsletter, available in both English and Polish.Subscribe today! https://lcelektronik.com/lce-insider/?utm_source=&utm_medium=&utm_campaign=podcast
In today’s episode of LC INSIDER, we talk about something every Project Manager knows too well: documentation that actually works. Not the kind that collects dust or gets lost in folders, but the kind that helps teams make decisions faster, avoid mistakes, and build knowledge that stays in the company — even when people change, when sprints move fast, or when a project suddenly pivots.
Let’s start with a simple rule: one file equals one decision. It sounds minimalistic, and that’s the point. When we separate files for approving layers, changing materials, or adjusting test conditions, the whole story becomes clear. One decision, one document, no confusion. In large projects, this clarity is gold. It helps teams review, compare versions, and understand why something happened — even months later. It also makes audits so much easier. No more hunting through long documents trying to guess what changed, when it changed, and who decided it.
This material comes from the free LCE Insider newsletter, available in both English and Polish.Subscribe today! https://lcelektronik.com/lce-insider/?utm_source=&utm_medium=&utm_campaign=podcast